Skip to main content
Glama

Mark entries

mark_entries
Idempotent

Set read or starred flags on specific RSS entries, an entire feed, or both to manage unread and saved items.

Instructions

Set read/starred flags on specific entries, a whole feed, or both combined.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mark_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
readNoSet the read flag
feed_idNoRestrict the update to one feed (used for mark-all-read)
starredNoSet the starred flag
entry_idsNoEntries to update; omit to target a whole feed

Output Schema

NameRequiredDescriptionDefault
okYes
messageYes
affectedNoNumber of entries updated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety and repeatability are covered. The description only adds blast-radius options; it does not say that flags can be unset with false, that a feed-wide call can touch many entries at once, or what the response reports.

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?

A single short sentence, front-loaded with the action and flags before the scope options. Every clause carries information and nothing is redundant.

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?

An output schema and full annotation set relieve the description of explaining return shape and safety. However, with four optional parameters and no required ones, it leaves open edge cases: what happens if neither read nor starred is supplied, and whether feed_id and entry_ids can be combined or conflict.

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 all four parameters (read, starred, feed_id, entry_ids) are already self-documenting, including 'omit to target a whole feed'. The description restates the same targeting model without adding format or interaction detail, so the baseline of 3 applies.

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?

The description uses a specific verb ('Set') plus the affected flags ('read/starred') and enumerates the three scopes (specific entries, a whole feed, both). An agent can tell exactly what is mutated, though no sibling tool is named for contrast.

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?

Scope selection is implied ('specific entries, a whole feed, or both combined'), which maps to the entry_ids/feed_id combination, but there is no explicit instruction on when to prefer this tool over siblings like get_entry or list_entries, and no noted preconditions or exclusions.

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