Skip to main content
Glama

update_read_progress_bulk

Update reading progress for multiple bookmarks in parallel, enabling batch marking as read or tracking progress on related articles. Returns success count and any failures.

Instructions

Update reading progress for multiple bookmarks in parallel. Useful for batch-updating progress on a set of related articles or bulk-marking articles as read. Progress ranges from 0.0 (not started) to 1.0 (finished). 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>",
      "progress": "<progress>"
    },
    "name": "update_read_progress_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
progressYesReading progress as a decimal (0.0 = not started, 1.0 = finished)
bookmark_idsYesArray of bookmark IDs to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/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 well: it discloses parallel execution, the 0.0-1.0 progress scale, and that the response contains a success count plus failures, implying partial success rather than all-or-nothing. It does not address permissions, reversibility, or what happens if some IDs are invalid, so it stops short of full behavioral coverage.

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?

Four short sentences, front-loaded with purpose and closing with return behavior; no filler. The progress-range sentence partially duplicates the schema, a small redundancy.

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?

There is no output schema, and the description compensates by describing the return shape (success count and failures). For a two-parameter bulk mutation with no annotations, what is missing is batch-size limits and failure semantics detail, not core calling information.

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 description coverage is 100%, so both parameters are already documented. The description's only parameter-related content (the 0.0-1.0 range) merely repeats the schema's own bounds, adding no new semantics such as ID validity or array size expectations.

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 and resource ('Update reading progress for multiple bookmarks') and the word 'multiple'/'parallel' cleanly separates it from the singular update_read_progress sibling.

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 usage contexts ('batch-updating progress on a set of related articles or bulk-marking articles as read'), but never states when to prefer the singular update_read_progress instead, nor any size or batching limits that would guide tool selection.

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