Skip to main content
Glama

The world according to capital

Delete a bookmark

delete_bookmark
DestructiveIdempotent

Permanently delete a bookmark and its slug aliases, so its old URLs return 404. Call only after the user has confirmed this exact bookmark by title and slug. To take a bookmark off the site and keep it, use reject_bookmarks. Curator only.

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

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/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 largely covered. The description still adds genuinely new behavior: deletion cascades to slug aliases, old URLs break with 404 (irreversibility), and the caller must be a curator. It does not say what happens when the slug does not exist or how the confirmation should be obtained. Value added beyond annotations is real but narrow, so a 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, each doing distinct work: effect, precondition, alternative. The destructive consequence is front-loaded before the guardrail, which is the right ordering for a delete tool.

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?

With no output schema, an agent still knows the effect, the irreversibility, the required confirmation, the alternative, and the permission level. Minor gaps remain around error/not-found behavior and slug sourcing, but nothing essential to calling it correctly is missing.

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?

The single parameter has 0% schema description coverage, so the description must carry the load, and it only implies that slug identifies the bookmark via the confirmation sentence. It never states the slug format, whether it is the canonical or an alias slug, or where the agent should obtain it. Partial compensation for the coverage gap, hence a 3.

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 ('Permanently delete a bookmark') plus the concrete consequence ('its slug aliases, so its old URLs return 404'), and explicitly separates it from the sibling that sounds similar (reject_bookmarks). An agent can distinguish this from every listed sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ('Call only after the user has confirmed this exact bookmark by title and slug'), names the alternative and its selection condition ('To take a bookmark off the site and keep it, use reject_bookmarks'), and states an access constraint ('Curator only'). When-to-use, when-not-to-use, and prerequisites are all present.

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