Skip to main content
Glama

unstar_bookmarks_bulk

Remove stars from multiple Instapaper bookmarks at once to deprioritize groups of articles. Returns a success count and reports any failures.

Instructions

Remove stars from multiple bookmarks in parallel. Use this to deprioritize a group of articles at once. Returns success count and any failures.

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_ids": "<bookmark_ids>"
    },
    "name": "unstar_bookmarks_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmark_idsYesArray of bookmark IDs to unstar

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses concurrency ("in parallel") and that the response includes a success count plus failures, implying partial-failure semantics rather than all-or-nothing. It says nothing about batch size limits, permission requirements, or what happens when an ID is already unstarred or invalid.

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?

Three short sentences, action first, then usage context, then return shape. No redundant or filler wording.

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 simple one-parameter batch tool with no output schema, the description covers purpose, use case, and return shape adequately. The remaining gap is the absence of any batch-size or error-handling detail for a bulk 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% for the single bookmark_ids parameter, so the schema already documents the array of numeric IDs. The description adds only "multiple" and the parallel-execution implication, with no constraints on array length or ordering.

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 ("Remove stars from multiple bookmarks") plus a batching mode ("in parallel"), which clearly separates it from the singular unstar_bookmark sibling. It stops short of naming that sibling explicitly, so the differentiation is implied by "multiple" rather than stated.

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 deprioritize a group of articles at once" gives a plausible use context, but there is no explicit when-not guidance and no named alternative for the single-bookmark case, even though unstar_bookmark exists.

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