Skip to main content
Glama
NewsCatcher MCP

NewsCatcher MCP

Official

Count articles over time

count_articles
Read-onlyIdempotent

Count exact news articles over time for up to five boolean queries, producing daily, weekly, or monthly timelines and share-of-voice comparisons for trend and spike analysis.

Instructions

Exact article counts over time for 1–5 boolean queries: a daily, weekly or monthly timeline of news volume, and share of voice between queries (companies, brands, topics). Use it for trends, spikes, "is coverage rising", comparing competitors, or charting attention around an event. Each bucket × query is one 5-credit call (at most 60 calls), so a 30-day daily timeline for 2 queries is 60 calls / 300 credits and takes about a minute.

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": {
      "queries": "<queries>",
      "from": "<from>"
    },
    "name": "count_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the period: ISO date or "today"/"yesterday" (default: now).
fromYesStart of the period: ISO date ("2026-09-01") or relative ("14d", "30 days ago"); up to 12 months back.
formatNotext (default, compact) or json (machine-readable).text
queriesYes1 to 5 boolean queries to count (same syntax as list_articles), e.g. ["Tesla", "Rivian", "Lucid"] for share of voice.
sourcesNoOnly these publishers: domains, e.g. ["reuters.com","ft.com"].
intervalNoBucket size: day (default), week or month.day
countriesNoOnly publishers from these countries: ISO 3166-1 alpha-2 codes, e.g. ["US","GB"].
languagesNoOnly these languages: ISO 639-1 codes, e.g. ["en","de"].
search_inNoWhere queries are matched (default title_body). Use ["title"] to count only headline mentions.
exclude_sourcesNoLeave out these publishers (domains).
exclude_countriesNoLeave out publishers from these countries (ISO 3166-1 alpha-2).
exclude_languagesNoLeave out these languages (ISO 639-1).
exclude_duplicatesNoLeave out syndicated copies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely valuable non-annotation context: per-call credit cost, a hard cap of 60 calls, and roughly a minute of latency, which lets an agent budget a request before issuing it.

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?

Three sentences, front-loaded with what the tool produces, then use cases, then cost. No filler; the credit arithmetic is compact and directly actionable despite being the longest sentence.

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 13-parameter aggregation tool with no output schema, the description covers purpose, granularity, cost and latency well. It is slightly thin on what happens when the 60-call ceiling is exceeded and on the shape of the returned timeline, though the format parameter partly signals output.

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 13 parameters are already documented in the schema, including interval, search_in and the exclude_* filters. The description only reinforces the queries parameter by framing multiple queries as share of voice, which is a modest addition over the structured data.

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 ('Exact article counts over time') plus the scope (1-5 boolean queries, day/week/month buckets, share of voice). This clearly separates it from retrieval siblings like list_articles or search_news, which return articles rather than aggregated counts.

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 explicit positive triggers: trends, spikes, 'is coverage rising', competitor comparison, charting attention around an event. It does not name an alternative tool or state when NOT to use it (e.g. when you need the actual articles, use list_articles), which keeps it short of a 5.

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