Skip to main content
Glama

Rename or move a page

update_page
DestructiveIdempotent

Changes a page's menu title, its search description, or its place in the menu (0 is first). Saved as a new draft version.

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": {
      "site_id": "<site_id>",
      "page_id": "<page_id>"
    },
    "name": "update_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
page_idYesThe page id from get_site.
site_idYesThe site id from list_sites or create_site.
positionNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The sentence 'Saved as a new draft version' is real added value beyond the annotations: it tells the agent the change does not go live and that a draft version is created. Combined with destructiveHint=true and idempotentHint=true, the effect is clear. It stops short of saying what happens to the previously published version or how the draft is later published.

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

Conciseness5/5

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

Two short sentences with no waste; the mutatable fields come first and the draft-version consequence is front-loaded in the second sentence, with the positional hint neatly parenthesized.

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 5-parameter mutation with no output schema, the definition covers what changes, the position convention, and the draft side effect. The remaining gap is the lack of any statement about the response or about how the draft becomes live, which publish_site presumably handles.

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

Parameters3/5

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

Schema coverage is only 40%, but the description compensates for the three optional parameters by mapping them to concepts (menu title, search description, place in the menu) and clarifying that position 0 means first. It adds little beyond that for title/description constraints, which the schema already caps via maxLength.

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

Purpose4/5

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

States a specific verb and resource ('Changes a page's menu title, its search description, or its place in the menu') that precisely enumerates the mutatable fields. It is clearly distinguishable from add_page/delete_page by the required existing page and the field list, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the tool edits an existing page (requires site_id and page_id), so an agent can infer it is not for creating pages. There is no explicit when-to-use/when-not guidance and no pointer to alternatives such as add_page or publish_site.

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