Skip to main content
Glama

star_bookmarks_bulk

Mark multiple Instapaper bookmarks as starred in parallel to prioritize important articles. Returns success count and any failures.

Instructions

Mark multiple bookmarks as starred in parallel. Use this to quickly highlight a set of important articles you want to track or prioritize. 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": "star_bookmarks_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmark_idsYesArray of bookmark IDs to star

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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, and it does disclose two useful traits: parallel execution and a return of success count plus failures, implying partial success is possible. It does not state whether already-starred IDs count as failures, whether the operation is idempotent, or any permission/size constraints on the array.

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 with the action front-loaded and the return behavior last, which is a sensible order. The middle sentence is slightly marketing-flavored but does carry usage context, so little is wasted.

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 bulk mutation tool with no annotations and no output schema, disclosing the return shape (success count and failures) is a meaningful completeness win. However, partial-failure semantics and preconditions for the batch remain unaddressed, which matters for a parallel write 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 array, so the schema already defines its type and purpose. The description adds no extra meaning such as maximum batch size, duplicate handling, or whether non-existent IDs are skipped versus reported as failures. Baseline 3 applies.

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 uses a specific verb+resource combination ('Mark multiple bookmarks as starred') and signals bulk/parallel semantics, which distinguishes it from the singular star_bookmark. It stops short of explicitly naming that sibling, so the differentiation is implied by plurality 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?

It offers a usage motivation ('quickly highlight a set of important articles you want to track or prioritize'), which is context for when to reach for bulk rather than single-star. There is no when-not guidance, no mention of using star_bookmark for a single ID, and no guidance on batch size limits.

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