Skip to main content
Glama

star_bookmark

Mark a bookmark as starred to highlight important Instapaper articles and track favorite reads in your library.

Instructions

Mark a bookmark as starred/important. Starring articles highlights them in your Instapaper library and helps you track your favorite or most valuable reads.

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

Input Schema

NameRequiredDescriptionDefault
bookmark_idYesID of the bookmark to star

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?

No annotations are provided, so the description carries the full burden. It correctly discloses the effect of starring (highlighting in the library), but omits whether the call is idempotent when the bookmark is already starred, what happens with an invalid ID, whether the prior starred state is recoverable, and what the response contains.

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, front-loaded with the action. The second sentence is partly promotional, but it does convey where the effect is visible, so it earns most of its space.

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 mutation tool with no output schema, the description covers what it does and its visible effect, but leaves behavioral edge cases (already starred, missing bookmark, return value) unspecified. Adequate but with clear gaps.

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?

Only one parameter exists and its schema description ("ID of the bookmark to star") already covers it at 100% coverage, so the schema baseline applies. The description adds the conceptual meaning of the starring operation but no additional detail about the identifier's format.

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?

States a specific verb and resource: "Mark a bookmark as starred/important." The singular "a bookmark" plus the verb makes it distinguishable from star_bookmarks_bulk and unstar_bookmark, but the description never names those siblings 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?

Usage is only implied through the benefit statement ("helps you track your favorite or most valuable reads"). There is no explicit when-to-use versus unstar_bookmark or the bulk variant, and no preconditions such as the bookmark needing to exist.

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