Skip to main content
Glama
NewsCatcher MCP

NewsCatcher MCP

Official

Get monitor updates

get_monitor_updates
Read-onlyIdempotent

Retrieve a monitor's delivered rows or stories from its latest or specified run, marked new or updated; company monitors can return the full story feed over recent days.

Instructions

What a monitor delivered: the new (or grown) rows or stories of its latest run, or of a given run_id, each marked new or update. For a company monitor, feed=true instead returns the full story feed of its companies over the last days. Free.

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": {
      "monitor_id": "<monitor_id>"
    },
    "name": "get_monitor_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWith feed=true: days of stories (default 7).
feedNoCompany monitors: every story of the last `days` instead of one run's delivery.
limitNoRows or stories to show (default 25).
formatNotext
run_idNoA specific monitor run (default: the latest).
monitor_idYesThe monitor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds real value beyond them: the cost signal ("Free"), the fact that results are tagged new versus update, and that feed=true is scoped to company monitors. It omits anything about pagination behavior or how the limit interacts with a large feed.

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 return semantics front-loaded and the feed special case immediately after. The parenthetical "(or grown)" and "marked new or update" are slightly compressed phrasing that could invite misreading, which keeps it off a 5.

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?

With no output schema, the description carries the burden of explaining return values and does so — rows/stories tagged new or update, or a full story feed under feed=true. It also removes cost ambiguity. What remains unaddressed is the text-versus-json output distinction and how much of a large feed is returned.

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 83%, so the parameters already document themselves, including the feed/days/run_id defaults and the limit bounds. The description largely restates what the schema says ("feed=true … returns the full story feed … over the last `days`") and does not explain the format enum or what json output looks like. 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?

The description states precisely what is returned: the rows or stories a monitor delivered in its latest run (or a specified run_id), each flagged as new or update. That is a specific resource-plus-scope statement that an agent can distinguish from get_monitor's configuration read without opening the schema. It falls short of 5 only because it never names a sibling or explicitly contrasts itself with get_monitor/get_story.

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?

It gives clear conditional guidance on mode selection: use the default for one run's delivery, use run_id for an older run, use feed=true for a company monitor's full story feed over `days`. However, that is intra-tool parameter routing rather than tool-selection guidance — nothing tells the agent when to prefer this over get_story, get_monitor, or search_news.

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