Skip to main content
Glama

unstar_bookmark

Removes the star from a saved Instapaper bookmark when it is no longer a favorite or should be deprioritized in your library.

Instructions

Remove the star from a bookmark. Use this when an article is no longer a favorite or needs to be deprioritized in your library.

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

Input Schema

NameRequiredDescriptionDefault
bookmark_idYesID of the bookmark to unstar

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, yet it discloses nothing about idempotency, what happens if the bookmark is not starred, error behavior on a bad ID, or whether the action is reversible via star_bookmark. For a simple toggle this is a modest but real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero padding, with the action stated first and the triggering condition second. Nothing needs trimming or reordering.

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 toggle with a fully described schema and no output schema, the description covers purpose and usage sufficiently. The remaining gap is behavioral edge cases, which matters less here than it would for a destructive or multi-parameter tool.

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?

The single parameter is fully documented in the schema (100% coverage, 'ID of the bookmark to unstar'), so the baseline is 3. The description only loosely links bookmarks to 'an article' and adds no format or sourcing detail beyond the schema.

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 names the exact verb+resource pair: 'Remove the star from a bookmark.' That is unambiguous and inherently distinguishable from the opposite operation, star_bookmark, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

It supplies clear when-to-use context ('no longer a favorite or needs to be deprioritized'), which is more than implied usage. It stops short of naming exclusions or the bulk alternative (unstar_bookmarks_bulk) for multi-item cases.

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