Skip to main content
Glama

Update a section

update_section
DestructiveIdempotent

Changes one section on a page. Only the fields you pass change; a list field (such as items) is replaced as a whole. The change goes into the draft and is saved as a new 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>",
      "section_id": "<section_id>",
      "data": "<data>"
    },
    "name": "update_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesThe fields to change for this section type. See list_templates for the fields.
page_idYesThe page id from get_site.
site_idYesThe site id from list_sites or create_site.
section_idYesThe section id from get_site.

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?

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: partial/patch semantics ('Only the fields you pass change'), wholesale replacement of list fields like items, and the draft-plus-new-version save model that follows from versioning siblings. It does not state permission requirements or what the response contains, which keeps it below a 5.

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?

Three short sentences, zero filler, and the identity of the operation is front-loaded before the non-obvious patch and versioning caveats. Every sentence carries information an agent would not get from the structured fields.

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 destructive, nested-payload mutation with no output schema, the definition covers the crucial unknowns: partial update semantics, list replacement, and the draft/version outcome. The remaining gap is the return value and any error or permission behavior, which nothing else in the supplied metadata supplies.

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 100%, so all four parameters are documented in the schema, establishing a baseline of 3. The description does add real meaning for the free-form 'data' object by clarifying patch semantics and list-field replacement, but it defers field discovery to list_templates rather than clarifying the nested payload itself.

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 first sentence names a specific verb and resource ('Changes one section on a page') and scopes it to a single section, which distinguishes it from page-level siblings like update_page and from add_section/remove_section. It stops short of naming any alternative explicitly, so an agent must infer the boundary from the noun alone.

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?

Use is implied by the verb 'Changes' plus the constraint that it targets one existing section, so the agent can infer this is for modifying an existing section rather than creating or removing one. However, there is no explicit when-to-use statement, no prerequisite (such as needing section_id from get_site), and no guidance on preferring it over update_page for bulk edits.

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