Skip to main content
Glama

Update Your page

page_update
Idempotent

Update Your page fields (not the launch page: use launchpad_update). Arrays replace existing values. Publishing (published: true) needs the person's approval and confirm_publish: true. Without it, edits to a page that is already published are saved as a draft and the public page keeps its approved version. Automatic checks may hold changes for review; inspect pending_review, moderation_status and owner_reason before claiming publication. Requires a claimed handle; Free must show the badge. HTTPS destinations and contrast are enforced by the API. Requires API key scope: draft.

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": {
      "updates": "<updates>"
    },
    "name": "page_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYes
confirm_publishNotrue only after the person explicitly approved publishing; required whenever this call publishes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / updates / properties / theme / properties / motion
      Added value: +{
      +  "description": "How much the page moves. lively (default): gentle entrance, button lift, signup shine, a small celebration on joining. subtle: soft fade and small hover lifts. off: no movement. Visitors who ask their device for reduced motion always get none.",
      +  "enum": [
      +    "lively",
      +    "subtle",
      +    "off"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, idempotent, non-destructive) by disclosing the real behavioural hazards: arrays replace rather than merge, edits to an already-published page silently become drafts while the public version stays live, and automatic checks can hold changes for review. It also names the moderation fields to inspect before claiming publication and the enforced constraints (HTTPS destinations, contrast).

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?

Five dense sentences with the sibling disambiguation and replacement rule front-loaded, and every sentence carrying a distinct operational fact. The telegraphic fragments ('Free must show the badge', 'Requires API key scope: draft') are compact at the cost of a little readability.

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 mutating, nested-schema tool with no output schema, it covers preconditions, publish gating, moderation side effects and the fields to read back. What it does not cover is the general shape of the response after a successful update, though the pending_review/moderation_status/owner_reason mention partly fills that gap.

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?

With only 50% schema coverage and a heavily nested updates object, the description compensates by explaining replacement semantics, the need to read page_get and resend existing section ids, and the meaning of confirm_publish. It still does not survey the updates sub-fields (theme, info, socials), leaving much of the nested schema to speak for itself.

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 ('Update Your page fields') and immediately disambiguates from the nearest sibling ('not the launch page: use launchpad_update'). An agent can route between page_update and launchpad_update without opening either schema.

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?

Gives concrete when-to-use routing (launchpad_update for the launch page, page_get before section edits), prerequisites (claimed handle, Free badge, draft API scope) and the publish precondition (person's approval + confirm_publish). It does not explicitly cover when to use page_update versus the page_link_* tools, which is the main gap.

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