Skip to main content
Glama

unarchive_bookmarks_bulk

Restore multiple archived bookmarks to your unread list in one bulk operation and return success counts plus any failures.

Instructions

Restore multiple bookmarks from archive in parallel. Use this to bring back a group of articles to your unread list. 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": "unarchive_bookmarks_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmark_idsYesArray of bookmark IDs to unarchive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the full behavioral burden. It does add two genuinely useful facts — execution happens "in parallel" and the result reports "success count and any failures" (i.e. partial failure is possible) — but it omits permissions requirements, batch size limits, and what happens to IDs that are already unarchived.

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, zero filler, with the core action and scope front-loaded before usage and return-shape notes.

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 bulk mutation with no annotations and no output schema, the description covers the essentials (action, use case, concurrency, partial-failure return) but leaves the caller guessing on error semantics and any per-call item limits.

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 ("Array of bookmark IDs to unarchive"), so the schema already explains it fully. The description adds no format or constraint detail beyond that, making the baseline 3 appropriate.

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?

"Restore multiple bookmarks from archive" is a specific verb plus resource, and the word "multiple" distinguishes it from the singular sibling unarchive_bookmark. It stops short of naming that sibling explicitly, but the bulk-vs-single contrast is still legible.

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?

"Use this to bring back a group of articles to your unread list" gives a concrete when-to-use scenario, so an agent knows the intent without inference. There are no stated exclusions or named alternatives (e.g. the singular tool for one item), which keeps it below a 5.

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