Skip to main content
Glama

delete_highlight

Remove a specific highlight from an Instapaper article by its ID to clean up excerpts you no longer need.

Instructions

Remove a specific highlight from an article. Use this to clean up highlights or remove excerpts you 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": {
      "highlight_id": "<highlight_id>"
    },
    "name": "delete_highlight"
  }
}

Input Schema

NameRequiredDescriptionDefault
highlight_idYesID of the highlight to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/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 for a destructive operation. It does not state that deletion is permanent or irreversible, whether the highlight must exist, what happens on an invalid ID, or what the response contains — all important for a remove operation with zero annotation coverage.

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?

Two short sentences with the action front-loaded and no filler wording. The second sentence is largely redundant with the first but is brief enough not to be a structural problem.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema, the definition covers what the tool does but omits the one thing an agent most needs for a delete: irreversibility and error behavior. Adequate to invoke, but incomplete for a destructive operation.

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% with a single parameter whose schema description ("ID of the highlight to delete") is adequate. The description adds no format, source, or lookup guidance for highlight_id, 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 states a specific verb and resource ("Remove a specific highlight") plus the owning container ("from an article"), which cleanly separates it from add_highlight and list_highlights. It stops short of naming a sibling or stating a scope constraint such as whether it works across articles, so it is clear but not maximally differentiated.

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

Usage Guidelines2/5

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

"Use this to clean up highlights or remove excerpts you no longer need" restates the deletion purpose rather than giving real routing guidance. There is no mention of where the highlight_id comes from (e.g., list_highlights), no when-not-to-use, and no alternative tool named, so an agent gets essentially no selection guidance beyond the name.

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