Skip to main content
Glama

Mark articles

update_articles
Idempotent

Mark articles from the user's feeds as read or unread, or save them to read later, by url. Several at once: "mark everything in crypto as read" is list_feed_items then this with every url.

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": {
      "urls": "<urls>"
    },
    "name": "update_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
readNotrue marks read, false marks unread.
urlsYesArticle urls from list_feed_items.
savedNotrue saves the article (a saved copy is kept even after the feed drops it), false unsaves it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / saved / description
      Previous value: -"true saves the article (a saved copy is kept even after the feed drops it)."New value: +"true saves the article (a saved copy is kept even after the feed drops it), false unsaves it."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare idempotent=true, destructive=false, readOnly=false and closed-world, so the safety profile is covered without the prose. The description adds the useful point that multiple urls can be processed in one call, but it never says what happens when neither 'read' nor 'saved' is supplied, nor whether saving also affects read state.

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?

Two compact sentences with the core action front-loaded and a concrete worked example appended. The example earns its place, though the phrasing 'is list_feed_items then this' is clipped and slightly informal.

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 mutation tool with no output schema, the definition covers the action, the batch pattern, and the parameter meanings well. It still leaves gaps on the default when neither flag is set and on what the response reports, which matters for a write operation.

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 coverage is 100% and the schema already explains read, saved (including that saved copies survive feed removal), and the 50-url cap. The description adds only the framing that urls come from list_feed_items, which is helpful context but not new parameter meaning, so the baseline 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?

States a specific verb and resource ('Mark articles from the user's feeds as read or unread, or save them'), plus the addressing key ('by url'). That separates it from list_feed_items and other siblings by resource, though it doesn't clarify how 'saved' relates to a potentially similar save/file 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 an explicit bulk workflow: 'mark everything in crypto as read' is list_feed_items then this with every url, which tells the agent both the prerequisite and the pattern for batch use. No when-not-to-use or exclusion guidance is offered, keeping 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources