Skip to main content
Glama

Remove page link

page_link_remove
DestructiveIdempotent

Permanently remove a page link. Ask for confirmation before calling; requires confirm: true. On a published page the change is saved as a draft and the public page keeps its approved version until the person approves publishing; then pass confirm_publish: true. Requires API key scope: draft.

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": {
      "id": "<id>",
      "confirm": "<confirm>"
    },
    "name": "page_link_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmYes
confirm_publishNotrue only after the person explicitly approved publishing; without it, changes to a published page wait as a draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the annotations by disclosing that removal is permanent, that on a published page the change lands as a draft while the public version stays live until approval, and that an API key scope of 'draft' is required. Those are exactly the side effects and authorization constraints an agent cannot derive from destructiveHint/idempotentHint alone.

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?

Front-loads the action, then the confirmation gate, then the published-page edge case, then the scope requirement. Every sentence conveys a distinct operational constraint with no filler.

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, three-parameter mutation with no output schema, the description covers permanence, the confirmation gate, the draft/publish side effect, and auth scope. It omits what happens to already-published links after approval and what errors to expect on a missing scope, but nothing essential to invoking it correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, so the description must carry weight, and it does: it establishes that confirm must be true and explains the approval-gated meaning of confirm_publish. The id parameter is never mentioned, and the confirm_publish explanation largely duplicates the schema's own description, so it isn't a full compensation.

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 ('Permanently remove a page link') and the adverb 'permanently' signals irreversibility. The remove/add/update distinction against siblings like page_link_add and page_link_update is inferable from the verb, though no sibling is named explicitly.

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?

Gives a concrete pre-call protocol ('Ask for confirmation before calling; requires confirm: true') and the condition under which confirm_publish becomes necessary. It stops short of naming alternatives (e.g. page_link_update for editing an existing link) or stating when removal is inappropriate.

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