Skip to main content
Glama

move_bookmark

Moves an Instapaper bookmark to a specified folder by bookmark ID and folder ID, so you can categorize saved articles into research or topic folders.

Instructions

Organize a bookmark by moving it to a specific folder. Use this to categorize articles (e.g., move research articles to a "UX Research" folder). Requires both the bookmark ID and target folder ID.

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>",
      "folder_id": "<folder_id>"
    },
    "name": "move_bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_idYesID of the destination folder
bookmark_idYesID of the bookmark to move

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole burden of behavioral disclosure. It identifies this as a state-changing operation, but it says nothing about whether the move is reversible, what happens if the target folder already contains the bookmark, what an invalid folder ID produces, or whether any special permissions are needed. For a mutation tool with zero annotation coverage, that is a meaningful gap.

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?

The description is short, front-loaded with the core action, and followed by a realistic example. The final sentence slightly restates what the schema already enforces as required, but it is brief enough not to feel wasteful.

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 simple two-parameter tool with a fully documented schema and no output schema, the definition covers the essentials. What it lacks is any side-effect or failure-mode context for an unannotated mutation, which leaves an agent without guidance on edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are clearly documented as bookmark ID and destination folder ID. The description reinforces that both are required, which is useful confirmation for a two-required-parameter call, but it adds no format, validation, or edge-case meaning 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 pairs a specific verb (move) with a specific resource (bookmark) and a destination (folder), reading as 'Organize a bookmark by moving it to a specific folder.' It is unambiguous on what the tool does, though it never contrasts itself with the single-bookmark scope against siblings that do similar work, such as move_bookmarks_bulk.

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 one concrete usage scenario ('move research articles to a "UX Research" folder'), which implies when to reach for it. However, it states no exclusions, prerequisites, or alternatives, so the agent must infer on its own that move_bookmarks_bulk is the choice for multiple bookmarks and that reordering folders is a different tool entirely.

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