Skip to main content
Glama

Add a section to a page

add_section

Adds a new section to a page, at the end or at a position (0 is the top). 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>",
      "section": "<section>"
    },
    "name": "add_section"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent mutation, and the description adds the genuinely non-obvious consequence: the result is "saved as a new draft version." That tells the agent the change is not live until publishing, which the annotations cannot convey. It stops short of saying whether prior versions are retained or whether concurrent edits conflict.

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?

A single short sentence with the action, placement options, index origin, and persistence effect all front-loaded. No redundant restatement of the name or title.

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?

For a mutation tool with a large nested section schema and no output schema, the description covers placement and draft persistence but omits the publish workflow and any constraints on which section types are valid. Adequate for a first call, but an agent must infer follow-up steps.

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 50%, and the description compensates for the undocumented `position` parameter with "0 is the top" and an implied default of appending at the end. The `section` parameter's semantics are entirely carried by the rich oneOf schema, so the description adds value for one gap but not the other.

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 ("Adds a new section to a page") plus the placement scope. It is distinguishable from update_section and remove_section by the verb alone, but never names them explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over update_section, add_page, or restore_version, and no prerequisites (e.g., whether the page must exist or be a draft). "At the end or at a position" describes the parameter, not when to use the tool.

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