Skip to main content
Glama

Remove a page from a Space

spaces_remove_note
Destructive

Take a page out of a Space's list. The page stays published, and the Space keeps its other pages and documents. Use it when the reader asks to drop a page from a Space; spaces_get_space lists the slugs in it. Needs the owner or editor role.

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": {
      "spaceId": "<spaceId>",
      "slug": "<slug>"
    },
    "name": "spaces_remove_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesA page slug from search_collection or get_note, for example "concepts/teaming/team-topologies".
spaceIdYesThe Space id, from spaces_list_spaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds the crucial blast-radius detail the annotations cannot express: the page remains published and the Space keeps its other pages and documents. It also discloses the authorization requirement (owner or editor role), which is exactly the kind of operational constraint annotations do not carry.

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 action and its most surprising property (the page stays published). Every sentence carries distinct information: effect, trigger, and prerequisite – nothing is redundant.

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 a fully described schema and destructive annotations, the description covers effect scope, role requirements, and input discovery. The only omission is any hint about what the call returns, which matters slightly more given there is no output schema.

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?

With schema coverage at 100%, the schema already documents both spaceId and slug, and the description never repeats that. It does add provenance value by naming spaces_get_space as a source for slugs, complementing the schema's mention of search_collection and get_note, though it adds nothing about the slug format or UUID constraint beyond the schema.

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 ("Take a page out of a Space's list") and immediately disambiguates it from a document-deletion operation by noting "The page stays published." An agent can tell this is an unlink/detach operation without opening the schema or comparing against spaces_add_note.

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 it when the reader asks to drop a page from a Space" gives an explicit trigger condition, and "spaces_get_space lists the slugs in it" points to the discovery path for required inputs. It stops short of an explicit when-not clause (e.g. don't use it to delete the page itself), so it is clear context rather than full routing guidance.

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