Skip to main content
Glama
NewsCatcher MCP

NewsCatcher MCP

Official

Update a monitor

update_monitor
Destructive

Pause, resume, edit, run now, or delete a news monitor—including its name, schedule, query, and companies—and resume with missed-story delivery to close coverage gaps.

Instructions

Change a monitor: pause or resume it, run it now, edit its name, schedule, query or companies, or delete it. Resume with fill_gap=true (default) to also deliver what it missed while paused (up to 30 days).

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": "update_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
queryNoCompany monitors: what to watch for ("" for every story). Dataset monitors: the research request.
actionNoWhat to do (default edit).edit
fill_gapNoWith resume: deliver what it missed while paused.
scheduleNoNew schedule.
companiesNoReplace its companies (not for monitors that follow a list).
monitor_idYesThe monitor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is known. The description adds real value by disclosing the fill_gap default on resume and the 30-day backfill window, but it never warns that delete is irreversible or that edit may overwrite existing fields — the highest-risk behaviors for a destructive tool remain unstated.

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?

Two dense sentences, front-loaded with the action list followed by the one subtle behavioral detail (resume backfill). No filler, no repetition of the title.

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 7-parameter destructive mutation with no output schema, the description covers the action space and the tricky resume semantics well. It leaves gaps around whether delete is permanent and whether edit replaces or merges fields — the schema partially compensates with per-field descriptions, but the delete risk is unaddressed anywhere.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86%, so the baseline is 3; the description earns an extra point by explaining that fill_gap defaults to true and that its effect is bounded to 30 days, which the schema does not say. It also maps the action enum to concrete edits (name, schedule, query, companies), though it mostly restates the enum values.

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 ("Change a monitor") and then enumerates the full action surface: pause, resume, run_now, edit name/schedule/query/companies, delete. An agent can tell this apart from create_monitor and get_monitor without opening any schema.

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 clear context for each action and a specific non-obvious rule for resume (fill_gap=true delivers missed items, capped at 30 days). It does not state when to prefer a sibling (e.g. get_monitor for reading, create_monitor for new monitors) or any exclusions, so it stops short of explicit alternatives.

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