Skip to main content
Glama

archive_bookmarks_bulk

Moves multiple Instapaper bookmarks to the archive in parallel to mark articles as done or hide them from the unread queue, returning success and failure counts.

Instructions

Move multiple bookmarks to archive in parallel. Use this to quickly mark a set of articles as done or hide them from your unread queue. 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": "archive_bookmarks_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmark_idsYesArray of bookmark IDs to archive

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 supplied, the description carries the full disclosure burden, and it does add real value by stating that operations run 'in parallel' and that the result reports a success count plus any failures, implying partial-failure tolerance. It says nothing about reversibility (unarchive), permission requirements, or rate limits, which are meaningful gaps for a mutation tool.

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, front-loaded with the action, followed by the use case and the return behavior. Nothing is redundant or padded.

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 bulk mutation with no output schema, the description covers the action, the intent, and the shape of the response (count plus failures), which is enough to invoke it correctly. The main omission is the undo path and any preconditions, which would matter given the absent annotations.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains bookmark_ids. The description only implicitly clarifies that these IDs correspond to 'articles' and that a whole set is processed at once; it adds no format or validation 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 states a specific verb and resource ('Move multiple bookmarks to archive') and the word 'multiple' plus 'in parallel' signals it is the bulk counterpart to the singular archive_bookmark. It does not explicitly name siblings like move_bookmarks_bulk or unarchive_bookmarks_bulk, so the agent must infer the boundary, but the core action is unambiguous.

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 gives a use case ('quickly mark a set of articles as done or hide them from your unread queue'), which implies when to reach for it, but offers no when-not conditions and never routes the agent to the alternative bulk tools (move, unarchive, delete) that could be confused with archiving.

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