Skip to main content
Glama

list_highlights

Retrieve all highlights and excerpts from a specific Instapaper article by bookmark ID to review key passages and takeaways.

Instructions

Retrieve all highlights/excerpts saved from a specific article. Shows all the important passages you have highlighted in that bookmark, useful for reviewing key points and important takeaways.

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": "list_highlights"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmark_idYesID of the bookmark

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description must carry the full behavioral burden. 'Retrieve'/'Shows' correctly conveys a read-only, side-effect-free operation, but it says nothing about ordering, pagination, or what happens when a bookmark has no highlights versus an invalid bookmark_id — gaps an agent would want covered for a no-annotation tool.

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?

Short and front-loaded: the core action appears first, followed by a value framing. The second sentence partially restates the first ('all the important passages you have highlighted' vs 'all highlights/excerpts saved'), so a small amount of wording is not fully earning its place.

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 one-parameter read tool this is close to adequate, but with no output schema the description offers no hint of the return shape (fields per highlight, whether an empty list is possible). It covers the 'what' sufficiently while leaving the 'what comes back' unaddressed.

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?

Schema coverage is 100% for the single bookmark_id parameter, so the baseline is 3. The description adds a bit of meaning by tying the ID to 'a specific article' and clarifying that highlights are scoped to that one bookmark, though it introduces a slight bookmark/article terminology mismatch that the schema's 'ID of the bookmark' has to resolve.

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?

Specific verb+resource: 'Retrieve all highlights/excerpts saved from a specific article,' with the scope ('from a specific article') making clear it is not a global highlight listing. It never names the nearest alternative (e.g., list_bookmarks) so an agent must infer the boundary, which keeps it at 4 rather than 5.

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?

The phrase 'useful for reviewing key points and important takeaways' gives a motive for calling it, which implies the when-to-use context. There is no explicit guidance on when NOT to use it or which sibling to prefer for browsing bookmarks versus highlights, so guidance is implied rather than stated.

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