Skip to main content
Glama

Delete a hub's page

delete_knowledge_hub_page
DestructiveIdempotent

Use this when the user wants one page removed from a knowledge hub. It cannot be restored. 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": {
      "hubId": "<hubId>",
      "pageId": "<pageId>"
    },
    "name": "delete_knowledge_hub_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
hubIdYesThe knowledge hub's id.
pageIdYesThe page's id, as the hub's pages list gives it.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is largely covered structurally. The description does add genuinely new context beyond them: 'It cannot be restored' discloses irreversibility and 'Free' signals no cost/quota impact. It says nothing about required permissions or what happens to hub references, which keeps it at a solid but not rich 3.

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 short sentences, front-loaded with the selection condition followed by the two consequences that matter (irreversibility, cost). No filler or restatement of the schema.

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 full annotation coverage and no output schema, the definition supplies the essentials: when to use, irreversibility, and cost. Only permission or cascade concerns remain unaddressed, a minor gap 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 coverage is 100%, and the schema already explains both hubId and pageId, including that the page id comes from the pages list. The description adds no meaning about the parameters beyond what the schema provides, so the baseline 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?

The description names a specific verb-and-resource pair ('one page removed from a knowledge hub'), which clearly separates it from the hub-level delete in the sibling list. It stops short of naming any sibling explicitly, so the differentiation is implicit in 'one page' rather than stated.

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?

'Use this when the user wants one page removed from a knowledge hub' gives a concrete trigger condition for invocation. There are no exclusion clauses and no pointer to a non-destructive alternative such as update_knowledge_hub_page, so an agent must infer when to decline.

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