Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Update page settings

update_page_settings
Destructive

Modify page metadata such as name, slug, parent, position, display name, SEO and custom fields. Only the fields and languages you send are changed; omitted ones keep their current values.

Instructions

Update page metadata: name, slug, parent and position in the tree, display name, SEO fields and custom fields. Only the languages and fields you pass change - the ones you omit keep their current values.

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": {
      "pageId": "<pageId>"
    },
    "name": "update_page_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoInternal page name
slugNoURL slug
orderNoPosition among the siblings under the (new or current) parent, 0-based. Siblings shift to make room; this is the order the page tree and any tree-driven navigation show.
pageIdYesPage id or slug
parentIdNoMove the page under a different parent by id or slug (reparent). The full slug path is recomputed from the new parent + this page's leaf segment, and descendant slugs cascade.
seoTitleNoSEO title for the languages you pass; languages you omit keep their current value
displayNameNoDisplay name for the languages you pass; languages you omit keep their current value
seoKeywordsNo
customFieldsNoCustom field values to set: [{ fieldKey, value }]. Fields you omit keep their current value
seoDescriptionNoSEO description for the languages you pass; languages you omit keep their current value

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / order
      Added value: +{
      +  "description": "Position among the siblings under the (new or current) parent, 0-based. Siblings shift to make room; this is the order the page tree and any tree-driven navigation show.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / pageId / description
      Previous value: -"Page id"New value: +"Page id or slug"
    • changedInput schema / properties / parentId / description
      Previous value: -"Move the page under a different parent by id (reparent). The full slug path is recomputed from the new parent + this page's leaf segment, and descendant slugs cascade."New value: +"Move the page under a different parent by id or slug (reparent). The full slug path is recomputed from the new parent + this page's leaf segment, and descendant slugs cascade."
    • addedInput schema / required
      Added value: +[
      +  "pageId"
      +]
  2. First observedv0.73.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so safety is known; the description's real contribution is patch semantics ('only the languages and fields you pass change'). It does not explain why the operation is destructive — e.g. that reparenting recomputes slug paths and cascades to descendants, which is left entirely to the schema. Given destructiveHint=true, that consequence should surface in the description.

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 compact sentences, zero filler. The editable surface is front-loaded and the partial-update rule follows as the key operational caveat.

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

Completeness3/5

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

With 10 parameters, nested objects and no output schema, the definition is adequate but thin for a destructive tool. It never states permissions or lock requirements, what the response contains, or the slug-cascade side effect of reparenting — all things an agent needs before committing a destructive change.

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 90%, so the schema already documents nearly every parameter in detail, including order shifting and parent reparenting. The description restates the field list and the omit-keeps-current rule but adds no format or behavioral detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description gives a specific verb (Update) plus resource (page metadata) and enumerates the exact editable surface: name, slug, parent, tree position, display name, SEO and custom fields. That enumeration implicitly separates it from siblings like update_page_blocks or update_page_layout (content/layout rather than metadata), though no sibling is named 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 only implied: an agent can infer this is for changing settings on an existing page, and the second sentence clarifies that it is a partial update. There is no explicit when-to-use versus create_page, update_page_type, or publish_page, and no prerequisites (e.g. page lock) are mentioned.

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

Deploy Server

Other Tools