Skip to main content
Glama

Update page draft

update_page_draft
Destructive

Write changes to a private MyReach draft; the published page stays unchanged until owner approval. Use linkUpdates for targeted edits, including mixed-card pages. links replaces the complete link-only list, and socials replaces the complete social-icon list, so omitted entries in either replacement are removed. Other omitted fields stay unchanged. Requires the latest expectedRevision. secondaryLanguages enables up to two languages besides English; profileTranslations and link translations merge supplied text for enabled languages. Frozen themes stay locked. Commerce, domains, calendars and file uploads are unsupported.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "draftId": "<draftId>",
      "expectedRevision": "<expectedRevision>",
      "content": "<content>"
    },
    "name": "update_page_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
draftIdYes
draftCapabilityNo
expectedRevisionYes

Output Schema

NameRequiredDescriptionDefault
noteYes
slugYes
statusYes
draftIdYes
revisionYes
expiresAtYes
publicUrlYes
baseRevisionYes
draftCapabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / content / properties / design / properties / primary / pattern
      Previous value: -"^#[0-9a-f]{6}$"New value: +"^#[0-9a-fA-F]{6}$"
    • changedInput schema / properties / content / properties / design / properties / secondary / pattern
      Previous value: -"^#[0-9a-f]{6}$"New value: +"^#[0-9a-fA-F]{6}$"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the destructive and non-idempotent annotations, the description explains the key destructive behavior: links and socials replace complete lists, so omitted entries are removed. It also discloses approval gating, revision freshness, language limits, frozen-theme locking, and unsupported feature areas.

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?

The definition is dense but front-loaded with the most important safety and scope information. Most sentences earn their place, though the semicolon-heavy style makes some of the replacement and translation rules harder to scan than necessary.

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

Completeness4/5

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

For a complex nested mutation tool with an output schema, the description covers the critical behavioral constraints: approval gating, destructive replacement semantics, revision requirements, translation behavior, and unsupported areas. The main missing piece is an explanation of draftCapability and clearer parameter-level detail for the top-level identifiers.

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?

Top-level schema coverage is 0%, so the description must carry parameter meaning. It successfully clarifies the ambiguous content fields: linkUpdates patches by index, links/socials replace full lists, secondaryLanguages caps at two, and profileTranslations merges. It does not explain draftId or draftCapability, leaving a notable gap.

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?

The description opens with a specific verb and resource: writing changes to a private MyReach draft. It immediately distinguishes this from publication by stating the published page stays unchanged until owner approval, which separates it from siblings like request_publication_approval.

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

Usage Guidelines4/5

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

It gives concrete guidance on when to use linkUpdates versus full links/socials replacement, and notes that omitted fields stay unchanged while replacements delete omitted entries. It also states the expectedRevision requirement and lists unsupported areas. It does not explicitly contrast with create_page_draft, but the draft-update context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources