Skip to main content
Glama

delete_bookmark

Permanently removes a bookmark from Instapaper by its ID. Use this when a user wants to delete an article they no longer need; the action cannot be undone.

Instructions

Permanently remove a bookmark from Instapaper. This action cannot be undone. Use this when the user wants to delete an article they no longer need.

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

Input Schema

NameRequiredDescriptionDefault
bookmark_idYesID of the bookmark to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does disclose the single most important trait, that the removal is permanent and irreversible. It stops short of saying what else is affected (e.g., whether associated highlights are also removed), whether any confirmation or permission is needed, and what a successful call returns.

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?

Three short sentences with the destructive trait front-loaded immediately after the action, which is the right ordering for a delete tool. The final sentence is useful but partly restates the intent already implied by the verb, so it is efficient rather than maximally tight.

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 one-parameter delete tool with no output schema and no nested structures, the definition covers action, permanence, and intent well enough to call it correctly. The only real omission is what happens to dependent data such as highlights on the deleted bookmark.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains bookmark_id. The description adds no format, sourcing, or validation detail beyond it, which is consistent with the baseline for high-coverage schemas rather than a strength of the text.

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?

The description names a specific verb and resource ('Permanently remove a bookmark') and adds the scope qualifier 'from Instapaper', which immediately separates it from reversible siblings like archive_bookmark or move_bookmark. An agent can identify the operation without opening the schema.

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

Usage Guidelines3/5

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

It gives a when-to-use condition ('when the user wants to delete an article they no longer need'), which is real guidance rather than none. However, it never names the obvious alternative for the adjacent case — archiving a bookmark the user wants out of the way but not destroyed — so the delete-vs-archive decision is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.