Skip to main content
Glama

Pagetool

Remove a page from a site

remove_page
Destructive

Removes one page (not the home page) from your site, using the dashboard's recoverable delete: a version is saved first and the page can be restored. Signed-in accounts only. Free.

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_key": "<site_key>",
      "path": "<path>"
    },
    "name": "remove_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe page to remove, e.g. "/about". The home page cannot be removed.
site_keyYesThe site to remove a page from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the description's real contribution is qualifying that destructiveness: it is a recoverable dashboard delete that saves a version first and can be restored. It also adds auth and cost context. It does not address what happens when the page is already gone (relevant given idempotentHint=false).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence carrying the action, the exclusion, and the recoverability guarantee, followed by two short constraint fragments. Front-loaded and free of padding, though the fragments read slightly telegraphic.

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 mutation with no output schema, the description covers the safety profile, auth requirement, and the home-page limit. It is only missing what the call returns (for example, whether a version identifier is handed back for the restore path).

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%, and both parameters are already documented in the schema, including the home-page restriction on "path". The description adds no new syntax or format detail beyond what is structured, so the baseline 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?

"Removes one page (not the home page) from your site" gives a specific verb, resource, and scope bound, which is enough to separate it from add_page and replace_page_html. It does not explicitly name a sibling alternative, so it falls short of the top mark.

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?

The description supplies real prerequisites and exclusions: signed-in accounts only, free, and the home page cannot be removed. It stops short of saying which tool to use instead when the intent is to edit, archive, or remove an entire site.

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