Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

gdelt_tv_stationchart

Compare US TV news coverage across stations with result counts. Filter by time, show, captions, transcripts, or onscreen text to see which stations cover your topic.

Instructions

Compare US television news coverage across stations. Return a result-count comparison across the requested.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd of an absolute time window. Same formats as from.
fromNoStart of an absolute time window. Accepts YYYY-MM-DD, RFC3339, or GDELT's raw YYYYMMDDHHMMSS. Cannot be combined with timespan.
showNoLimit to an exact show name.
visualNoSearch visual object/activity labels from computer vision (GDELT's visual: operator). Repeatable; multiple values are OR'd together.
captionNoSearch human-provided closed captioning (GDELT's cap: operator). Repeatable; multiple values are OR'd together.
conceptNoSearch Google Knowledge Graph concepts extracted from captioning, by MID code (GDELT's capnlp: operator). Repeatable; multiple values are OR'd together.
stationYesRequired, repeatable. One or more stations, OR'd together.
timespanNoRelative time window ending now, e.g. 1h, 7d, 3m, 1y. Cannot be combined with from/to. Omit both for GDELT's full archive (auto-resolution, back to July 6, 2010).
transcriptNoSearch machine-generated speech-to-text transcripts (GDELT's asr: operator). Repeatable; multiple values are OR'd together. Short phrases only (GDELT caps each at 5 words).
onscreen_textNoSearch OCR'd onscreen text/chyrons (GDELT's ocr: operator). Repeatable; multiple values are OR'd together. Short phrases only (GDELT caps each at 5 words).
exclude_visualNoExclude clips whose visual labels match this value (GDELT's -visual: operator). Repeatable; every value must be absent.
exclude_captionNoExclude clips whose closed captioning matches this value (GDELT's -cap: operator). Repeatable; every value must be absent.
exclude_conceptNoExclude clips whose extracted concepts match this MID code (GDELT's -capnlp: operator). Repeatable; every value must be absent.
exclude_transcriptNoExclude clips whose speech-to-text transcript matches this value (GDELT's -asr: operator). Repeatable; every value must be absent.
exclude_onscreen_textNoExclude clips whose OCR'd onscreen text matches this value (GDELT's -ocr: operator). Repeatable; every value must be absent.
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It adds only that the tool 'returns a result-count comparison,' which is vague and incomplete; it does not explain what is counted, how filters affect counts, whether the comparison is per-station or aggregate, or any other behavioral traits. The truncated phrasing further reduces transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, which is good, but the second sentence is redundant and incomplete. It does not earn its place, and the truncation makes it feel sloppy rather than concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 15 parameters and no output schema, the description is far too thin. It does not explain the output structure, how to interpret the 'result-count comparison,' or how the many filter parameters interact with the station comparison. An agent would be guessing at the expected response shape and semantics.

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 the baseline is 3. The description itself adds no parameter details, but the schema already documents all 15 parameters thoroughly, so no compensation is needed.

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 a clear verb ('Compare'), a specific resource (US television news coverage), and a scope ('across stations') that distinguishes it from related sibling tools like gdelt_tv_showchart. However, the second sentence is grammatically truncated ('across the requested'), which slightly undermines clarity.

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?

The intended use is implied: compare coverage across stations. But there is no explicit guidance on when to choose this tool over siblings like gdelt_tv_showchart, gdelt_tv_timeline, or gdelt_tv_stationdetails, and no exclusions or alternatives are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server