Skip to main content
Glama

move_bookmarks_bulk

Move multiple Instapaper bookmarks to one folder in a single bulk operation, using parallel requests to organize large sets of articles after search or bulk discovery.

Instructions

Move multiple bookmarks to the same folder in parallel. While Instapaper API only supports single moves, this tool batches them efficiently using parallel requests. Ideal for organizing large sets of articles after search or bulk discovery. 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>",
      "folder_id": "<folder_id>"
    },
    "name": "move_bookmarks_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_idYesID of the destination folder for all bookmarks
bookmark_idsYesArray of bookmark IDs to move

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses the batching strategy (parallel requests over an API that only does single moves) and states the return shape (success count plus failures), which tells the agent partial failure is possible. It stops short of stating what happens on invalid folder IDs, whether moves are atomic, or any rate-limit concerns.

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 sentences, each doing distinct work: what it does, why it exists (API limitation), and when to use it, then the return contract. Front-loaded with the action and no redundant restatement of the name.

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 two-parameter bulk mutation with no output schema, the description covers purpose, execution model, intended use case, and return values. The remaining gap is failure semantics: it says failures are returned but not whether the operation is all-or-nothing.

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%, so both parameters are already fully documented and the baseline is 3. The description does add the useful semantic that folder_id is the single shared destination for every ID in the array, but it adds no format or constraint detail beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb, resource and scope: "Move multiple bookmarks to the same folder in parallel." The word "multiple" distinguishes it from the single-bookmark sibling move_bookmark without needing the schema, and the parallel-execution detail is stated up front.

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?

Gives a clear use context ("Ideal for organizing large sets of articles after search or bulk discovery") which orients the agent toward bulk scenarios. It implies single moves belong elsewhere by noting the API only supports single moves, but never names move_bookmark as the alternative or states an explicit when-not, so it falls short of a 5.

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