Skip to main content
Glama

Mark all read

mark_all_read
Destructive

Mark every article in a feed or folder as read, optionally only items older than a specified ISO date, to clear unread backlogs while respecting write limits.

Instructions

Mark all articles in a feed or folder as read. Costs 1 Zone 2 request. Base costs exclude safe-read retries (up to 4 attempts, each counted); honor cached status/cooldown. Never blindly replay uncertain writes. See inoreader://usage for limits, URI examples and prompts.

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": {
      "stream_id": "<stream_id>"
    },
    "name": "mark_all_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
beforeNoISO date - only mark items older than this as read (defaults to now)
stream_idYesStream ID of the feed or folder to mark as read

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.6.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / before / maxLength
      Added value: +128
    • addedInput schema / properties / before / minLength
      Added value: +1
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds substantive context they don't carry: cost of 1 Zone 2 request, up to 4 counted retry attempts, honoring cached status/cooldown, and a warning not to blindly replay uncertain writes. Only the exact effect on read state (irreversible? does it touch starred items?) is left unstated.

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?

Front-loaded with the core action in the first sentence, followed by quota and safety notes that are all relevant to correct invocation. The trailing resource pointer is useful but the middle sentences are terse to the point of being cryptic without the referenced resource.

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 two-parameter destructive write with no output schema, the definition covers cost model, retry accounting, and replay safety, which is most of what an agent needs. It could go further on what exactly is altered and whether the action can be undone, but the essentials are present.

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 in the schema. The description only adds the useful clarification that stream_id may reference a feed or folder, which is a marginal gain beyond the structured fields.

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 ('Mark ... as read') and resource scope ('all articles in a feed or folder'), with the word 'all' making the bulk nature explicit. No sibling tool performs this operation, so an agent can select it unambiguously.

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?

Usage context is implied by the operation itself (bulk-clearing unread state on a stream) and reinforced by operational warnings about cooldowns and replaying uncertain writes. However, it never states when to prefer this over narrower alternatives like batch_edit_subscriptions or per-article edits, nor any when-not conditions.

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