Skip to main content
Glama

PubSpace

by ai.pubspace
OverviewDiscussionsAdmin

Replace a page's content

update_page
DestructiveIdempotent

Replace the content of an existing page in place: the same URL serves the new content immediately, so links the human already shared keep working. Use this instead of publish_page whenever the page already exists. The previous version stays restorable from the dashboard for 7 days (Pro keeps full version history). Pass draft: true to stage the update instead: nothing changes for viewers until the maker reviews the previewUrl and presses "Sync to live"; use it when the human asked to see changes before they go out. Fails with page_not_found if the id is not a live or offline page in this space.

Input Schema

NameRequiredDescriptionDefault
htmlYesThe complete new document (not a diff). HTML, or Markdown when source_type is "markdown".
draftNoDefault false (publishes live instantly). true = stage the update; relay the returned previewUrl so the human can review and press Sync. A new draft replaces any pending one.
titleNoOptional; omit to keep the existing title.
page_idYesThe page id: the `id` field from publish_page or list_pages (also the last path segment of the page URL, …/docs/<page_id>). Only pages in the connected maker's space are visible.
projectNoOptional; omit to keep the existing project.
source_typeNoDefault "html".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / html / description
      Added value: +"The complete new document (not a diff). HTML, or Markdown when source_type is \"markdown\"."
    • changedInput schema / properties / page_id / description
      Previous value: -"The id returned by publish_page / list_pages."New value: +"The page id: the `id` field from publish_page or list_pages (also the last path segment of the page URL, …/docs/<page_id>). Only pages in the connected maker's space are visible."
    • addedInput schema / properties / source_type / description
      Added value: +"Default \"html\"."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well past the destructive/idempotent annotations: it discloses the 7-day restore window, Pro-tier history difference, the draft staging lifecycle (nothing live until the maker presses 'Sync to live'), and the specific page_not_found failure condition. This is exactly the extra context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and the sibling differentiator, then the draft workflow, then the error case. Dense and mostly waste-free, though the nested parentheticals make individual sentences long enough to skim poorly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description still tells the agent what comes back in the draft path (previewUrl) and the failure mode. For a destructive 6-parameter mutation, nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds workflow meaning beyond the schema: draft: true stages rather than publishes and the returned previewUrl must be relayed to the human. It does not add anything for title/project/source_type beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Replace the content of an existing page in place') and immediately clarifies the key consequence (same URL serves new content). It names the sibling it replaces (publish_page) so an agent can discriminate without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing rules: use this instead of publish_page whenever the page already exists, and pass draft: true 'when the human asked to see changes before they go out'. Both the alternative and the selecting condition are spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PubSpace toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources