Skip to main content
Glama

add_highlight

Mark important passages, quotes, or key insights in an Instapaper article by saving selected text at a specified character position for later reference.

Instructions

Add a highlight (excerpt) to an article. Specify the text to highlight and its position in the article. Use this to mark important passages, quotes, or key insights for later reference.

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>",
      "text": "<text>",
      "position": "<position>"
    },
    "name": "add_highlight"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to highlight
positionYesPosition in the article (character offset)
bookmark_idYesID of the bookmark

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 write operation. It says nothing about whether text must be an exact substring of the article, how position is validated, whether duplicate highlights are allowed, what permissions are needed, or what is returned on success.

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, front-loaded with the core action and followed by the required inputs and intent. Slight redundancy between "Specify the text to highlight and its position" and the schema, but nothing is padded.

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 simple three-parameter creation tool with no output schema, the description covers purpose and intent adequately. It falls short on the behavioral details an agent would want before writing data, such as text/position validation rules and interaction with the referenced 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?

Schema description coverage is 100%, so all three parameters are already documented in structured form, and the description adds only the framing that position is relative to the article. Baseline 3 is appropriate since the schema does the heavy lifting.

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 gives a specific verb and resource ("Add a highlight (excerpt) to an article") and parenthetically clarifies what a highlight is. It is immediately distinguishable from siblings like list_highlights or delete_highlight by the "add" verb, though it never names them explicitly.

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?

"Use this to mark important passages, quotes, or key insights for later reference" gives an implied usage context, but there is no when-not guidance, no prerequisites (e.g. must the bookmark already exist?), and no routing to alternatives such as add_bookmark or list_highlights.

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