Skip to main content
Glama

unarchive_bookmark

Restore an archived Instapaper bookmark to your unread list by bookmark ID so you can read or reconsider saved articles.

Instructions

Restore a bookmark from the archive back to your unread list. Use this to bring back articles you want to read or reconsider.

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

Input Schema

NameRequiredDescriptionDefault
bookmark_idYesID of the bookmark to unarchive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose the concrete state transition: the bookmark leaves the archive and returns to the unread list. It omits what happens if the bookmark is not archived, whether the operation is idempotent, and whether 'unread' status is reset, which keeps it short of a 5.

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?

Two sentences, the effect front-loaded and the rationale second, with no filler or repeated information from the schema.

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 one-parameter state-changing tool with no output schema, the description covers purpose and the resulting state, which is close to adequate. It falls short on preconditions, error behavior, and the single vs bulk distinction, which are relevant because no annotations fill those gaps.

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_id fully. The description adds only the conceptual framing of what id is being restored, not format, sourcing, or constraints.

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 ('Restore a bookmark from the archive') and names the resulting state ('back to your unread list'), which distinguishes it from the inverse archive_bookmark. It never explicitly contrasts with the sibling unarchive_bookmarks_bulk, but the singular framing makes the scope evident.

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?

Gives a use case ('bring back articles you want to read or reconsider'), which is implied when-to-use guidance. It does not state when not to use it or point to the bulk sibling for multi-bookmark restores, leaving the choice between single and bulk to inference.

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