Skip to main content
Glama

archive_bookmark

Moves a bookmark to the archive to clear it from the unread queue without deleting it; use it to mark articles as done or hide them temporarily, with unarchiving later.

Instructions

Move a bookmark to the archive. Archiving removes articles from your unread queue without deleting them, useful for marking articles as done or temporarily hiding them. The bookmark can be unarchived later.

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": "archive_bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmark_idYesID of the bookmark to archive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/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 burden and does disclose the essential behaviors: the bookmark leaves the unread queue, the underlying article is not deleted, and the action is reversible via unarchive. It does not cover edge behavior such as what happens when archiving an already-archived bookmark or whether authentication/permissions are required, which keeps it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and its effect, with no filler. There is mild redundancy between 'Move a bookmark to the archive' and the following 'Archiving removes...' sentence, but each sentence adds distinct information about consequences and reversibility.

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 single-parameter, non-destructive, reversible mutation, the description covers purpose, effect, and reversibility, which is what an agent needs to choose and invoke it. The absence of any note on failure modes or prerequisites is the only residual gap.

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?

Only one parameter exists and the schema already documents it at 100% coverage ('ID of the bookmark to archive'). The description restates the operation but adds no format, type, or source guidance for bookmark_id, so the baseline 3 is 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?

States a specific verb and resource ('Move a bookmark to the archive') and immediately clarifies the effect ('removes articles from your unread queue without deleting them'). This implicitly distinguishes it from delete_bookmark, but no sibling is named outright, so differentiation from archive_bookmarks_bulk or move_bookmark relies on the agent's inference.

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 concrete use contexts ('marking articles as done or temporarily hiding them') that tell the agent when this tool fits. It stops short of explicit exclusions or pointing to the alternatives (bulk archive, delete, unarchive) for opposing cases, which is why it is not a 5.

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