Skip to main content
Glama

Delete a page

delete_page
DestructiveIdempotent

Deletes a page from the site's draft. The home page cannot be deleted. 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>"
    },
    "name": "delete_page"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 still adds genuine behavior: deletion is scoped to the draft, the home page is protected, and prior versions survive and can be recovered via restore_version — meaningful facts the annotations do not carry. It leaves one important question open: whether an already-published page remains live after this call.

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 tight sentences with zero filler, and the destructive scope is stated first before the constraint and the recovery path. Every sentence carries information an 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?

For a two-parameter destructive tool with no output schema, the description covers the main risks: draft scope, an undeletable page, and recoverability. The one material gap is the effect on published content or any prerequisite (e.g., unpublishing first), which an agent would still have to discover.

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 both parameters are fully documented in the schema, including where each id comes from. The description adds no parameter-level detail, so the baseline of 3 applies.

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?

"Deletes a page from the site's draft" gives a specific verb and resource, and the draft scoping narrows it beyond a bare 'delete'. It is distinguishable from delete_site/delete_photo/delete_lead by resource, but the description never explicitly frames itself against those siblings, so it stays at a clear-but-undifferentiated 4.

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?

It states a concrete when-not condition (the home page cannot be deleted) and points to restore_version for recovery, which gives the agent real decision context. It does not address adjacent choices such as unpublishing versus deleting, so it falls short of full when/when-not/alternatives coverage.

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