Skip to main content
Glama

Remove a section

remove_section
DestructiveIdempotent

Removes one section from a page's draft. Earlier versions stay available through restore_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>"
    },
    "name": "remove_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is structured. The description adds two traits annotations cannot express: the change is confined to the draft (published page untouched) and it is recoverable via restore_version. It doesn't say what happens on a nonexistent or already-deleted section id, leaving a small gap.

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, no filler, with the scope restriction (draft) front-loaded before the recovery hint. Every clause carries information the agent needs.

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?

A simple three-parameter mutation with full schema coverage and annotations covering destructiveness; the description adds the draft scoping and reversibility that matter most. Only edge-case behavior (missing section, effect on already-published content) is unaddressed, which is minor for this complexity.

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 description coverage is 100% and each of the three ids already documents its source (get_site, list_sites/create_site). The description adds no syntax or constraint detail beyond the schema, so baseline 3 is appropriate.

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 ('Removes one section') and narrows the scope to 'a page's draft', which distinguishes it from sibling operations like delete_page (whole page) and update_section (modify in place). An agent can identify the operation without opening the 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?

Provides an implicit decision aid: destructive removal from the draft is safe to attempt because 'Earlier versions stay available through restore_version', pointing at the recovery path. It does not explicitly contrast with update_section or state when removal is preferable, so it falls short of a full when/when-not statement.

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