Update editorial settings

Outcome

Replaces stored workspace editorial and SEO default fields. This handler does not rewrite articles or inject those settings into direct API article creation; callers supply their chosen article fields. Sets or clears the linked Insights workspace when insightsWorkspaceId is supplied; omitting it keeps the current link. Linking grants no Insights access: each reader still needs their own access to that Insights workspace.

Before you start

• Verify identity and the intended environment with topolo whoami before selecting an explicitly authorized organization.
• Discover the published workspace:write permission.
• Discover an accessible Blog workspace and set WORKSPACE_ID to that exact returned id. Pass workspace binding separately from action input.
• Review the actual state change and confirm the unchanged plan before execution. Fixture ids and provider responses grant no live authority.

Discover the target

topolo whoami --json
topolo actions get app_topolo_blog.settings.update --detail --json
topolo workspaces list topolo-blog --json

• insightsWorkspaceId: Insights workspace id this Blog workspace reads readership from. Omit to keep the current link; an empty string unlinks. Analytics refuses with insights_workspace_not_linked while unlinked, and Insights checks each reader's own access to the linked workspace.

Request

PUT /api/settings

Inspect parameters and test this action.

Input fields

Worked examples

Documentation source snapshot: TopoloBlog 80d6961207a4ca688b7e9edb947dda720051ad32 (tree 534a285e739a27c1ea9e2c187ce8863824f6c590). The examples retain local fixture captures labeled baseline 2c64c35bf291a47bb3a0c597dcea46ccb47e2a08; their exact executed working tree is not established here. They were not rerun at this documentation snapshot. The production catalog marker topolo.app.json is not a deployed worker revision. Recovery metadata read-back on 18 October 2026 associates the current production Blog API and web deployments with this source through the 17 October release receipt. This establishes applicable deployed source; it does not make these examples current production captures.

Actual exported Blog Worker, local Miniflare D1/R2 and all committed migrations. Auth, Insights, DNS, Cloudflare for SaaS, error reporting, queue and scheduled-workflow boundaries are synthetic and outbound fetch is sealed. No deployed provider, delivery or scheduled execution outcome is established. English examples use the packaged test translation release; article checks and widget labels follow the verified request locale. No live translation release is proved by this fixture.

Save a reviewed input as payload.json. Replace fixture identifiers using discovery in the authorized context.

topolo actions validate app_topolo_blog.settings.update --data @payload.json --json
topolo actions plan app_topolo_blog.settings.update --resource-type workspace --resource-id "$WORKSPACE_ID" --data @payload.json --confirm --json
topolo actions call app_topolo_blog.settings.update --resource-type workspace --resource-id "$WORKSPACE_ID" --data @payload.json --confirm --detail --json

MCP uses the same reviewed input. Replace the synthetic workspace resourceId through discovery when a binding is shown:

{
  "tool": "topolo_prepare_action",
  "arguments": {
    "actionId": "app_topolo_blog.settings.update",
    "input": {
      "editorialName": "",
      "defaultAuthorName": "",
      "defaultSeoTitle": "",
      "defaultSeoDescription": "",
      "insightsWorkspaceId": "ws_insights_fixture"
    },
    "resourceType": "workspace",
    "resourceId": "ws_blog_fixture",
    "confirm": true
  }
}

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_blog.settings.update",
    "input": {
      "editorialName": "",
      "defaultAuthorName": "",
      "defaultSeoTitle": "",
      "defaultSeoDescription": "",
      "insightsWorkspaceId": "ws_insights_fixture"
    },
    "resourceType": "workspace",
    "resourceId": "ws_blog_fixture",
    "confirm": true,
    "detail": true
  }
}

Successful response · HTTP 200

Input · payload.json:

{
  "editorialName": "",
  "defaultAuthorName": "",
  "defaultSeoTitle": "",
  "defaultSeoDescription": "",
  "insightsWorkspaceId": "ws_insights_fixture"
}

Source-reviewed illustration (retained local fixture response; not a current production capture):

{
  "settings": {
    "editorialName": "",
    "defaultAuthorName": "",
    "defaultSeoTitle": "",
    "defaultSeoDescription": "",
    "insightsWorkspaceId": "ws_insights_fixture",
    "updatedAt": "2026-10-14T12:43:11.530Z"
  }
}

Call app_topolo_blog.settings.get and confirm the stored defaults and insightsWorkspaceId.

Successful response · HTTP 200

Input · payload.json:

{
  "editorialName": "Fixture editorial",
  "defaultAuthorName": "Fixture editor",
  "defaultSeoTitle": "Fixture Blog",
  "defaultSeoDescription": "Source-bound documentation examples."
}

Source-reviewed illustration (retained local fixture response; not a current production capture):

{
  "settings": {
    "editorialName": "Fixture editorial",
    "defaultAuthorName": "Fixture editor",
    "defaultSeoTitle": "Fixture Blog",
    "defaultSeoDescription": "Source-bound documentation examples.",
    "insightsWorkspaceId": "ws_insights_fixture",
    "updatedAt": "2026-10-14T12:43:13.905Z"
  }
}

Call app_topolo_blog.settings.get and confirm the stored defaults and insightsWorkspaceId.

Refused request · HTTP 401 · auth_error

Input · payload.json:

{
  "editorialName": "",
  "defaultAuthorName": "",
  "defaultSeoTitle": "",
  "defaultSeoDescription": "",
  "insightsWorkspaceId": "ws_insights_fixture"
}

Source-reviewed illustration (retained local fixture response; not a current production capture):

{
  "error": "Authentication token required"
}

Sign in again in the intended environment using a valid credential. Preserve the returned handler message; SDK auth_error can represent several authentication refusals.

Verify the result

• Call app_topolo_blog.settings.get and confirm the stored defaults and insightsWorkspaceId.

Errors and recovery

• HTTP 401 · auth_error: Sign in again in the intended environment using a valid credential. Preserve the returned handler message; SDK auth_error can represent several authentication refusals.

Inspect the raw handler error as well as the SDK code. These examples establish observed local refusals, not every possible provider failure.

Recovery boundary

Send the previous settings back. Read them first — this replaces rather than merges.

Evidence

Actual exported Blog Worker, local Miniflare D1/R2 and all committed migrations. Auth, Insights, DNS, Cloudflare for SaaS, error reporting, queue and scheduled-workflow boundaries are synthetic and outbound fetch is sealed. No deployed provider, delivery or scheduled execution outcome is established. English examples use the packaged test translation release; article checks and widget labels follow the verified request locale. No live translation release is proved by this fixture.

Documentation history

18 October 2026: Architecture reviewed the retained action guide against the pinned source declaration and named implementation boundaries, qualified local-capture provenance, and prepared paired human and agent amendments. This review does not record a product release, new fixture execution or publication.

2026-10-18: Architecture reaccepted this guide against the corrected published settings declarations and the retained 80D deployed-source association. The prior catalog/dependency content hold is resolved for this exact payload. Examples remain source-reviewed illustrations, not new production captures. No business settings or analytics request, guide publication or new deployment is recorded.