Crawlora MCP

gdelt_tv_showchart

Read-only

Return ranked show-share rows showing which US TV programs account for the largest share of matching GDELT clips. Supply required stations from gdelt_tv_stationdetails and the same caption/transcript/concept/OCR/visual filters as gdelt_tv_search; TV results may lag broadcasts by 24-48 hours. Use gdelt_tv_stationchart to compare stations, gdelt_tv_timeline for airtime over time, or gdelt_tv_wordcloud for term frequencies.

Input Schema

Name	Required	Description
`to`	No	End of an absolute time window. Same formats as from.
`from`	No	Start of an absolute time window. Accepts YYYY-MM-DD, RFC3339, or GDELT's raw YYYYMMDDHHMMSS. Cannot be combined with timespan.
`show`	No	Limit to an exact show name.
`visual`	No	Search visual object/activity labels from computer vision (GDELT's visual: operator), e.g. VOLCANO, POLICE. Repeatable -- multiple values are OR'd together.
`caption`	No	Search human-provided closed captioning (GDELT's cap: operator). Repeatable -- multiple values are OR'd together.
`concept`	No	Search Google Knowledge Graph concepts extracted from captioning, by MID code (GDELT's capnlp: operator), e.g. /M/0d063v. Repeatable -- multiple values are OR'd together.
`stations`	No	Required, repeatable. One or more stations, OR'd together. Allowed values: CNN, MSNBC, FOXNEWS, BBCNEWS, KGO (ABC San Francisco), KPIX (CBS San Francisco), KNTV (NBC San Francisco). See gdelt-tv-stationdetails for GDELT's own current list.
`timespan`	No	Relative 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).
`transcript`	No	Search 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_text`	No	Search 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_visual`	No	Exclude clips whose visual labels match this value (GDELT's -visual: operator). Repeatable; every value must be absent (AND'd exclusions).
`exclude_caption`	No	Exclude clips whose closed captioning matches this value (GDELT's -cap: operator). Repeatable; every value must be absent (AND'd exclusions).
`exclude_concept`	No	Exclude clips whose extracted concepts match this MID code (GDELT's -capnlp: operator). Repeatable; every value must be absent (AND'd exclusions).
`exclude_transcript`	No	Exclude clips whose speech-to-text transcript matches this value (GDELT's -asr: operator). Repeatable; every value must be absent (AND'd exclusions).
`exclude_onscreen_text`	No	Exclude clips whose OCR'd onscreen text matches this value (GDELT's -ocr: operator). Repeatable; every value must be absent (AND'd exclusions).

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / stations / items / description
```
Added value: +"Documented values: CNN, MSNBC, FOXNEWS, BBCNEWS, KGO, KPIX, KNTV."
```
First observedOct 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior the annotations don't: TV results may lag broadcasts by 24-48 hours, and stations must come from gdelt_tv_stationdetails. Good added context, though it doesn't describe ranking semantics or how results are ordered beyond 'largest share.'

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 returns, then the required input, then the sibling routing. Every sentence carries distinct information with no filler.

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

Completeness5/5

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

An output schema exists, so return values need no exposition, and annotations cover the safety profile. The description supplies purpose, requirements, latency caveat, and alternatives — everything an agent needs to invoke this correctly with 15 parameters.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by declaring `stations` effectively required (despite the empty required array) and pointing to gdelt_tv_stationdetails for values, plus noting the filter set mirrors gdelt_tv_search. This routing information is not in the schema.

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 with precise output: 'ranked show-share rows showing which US TV programs account for the largest share of matching GDELT clips.' This immediately distinguishes it from the sibling chart/timeline/wordcloud tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names three explicit alternatives with the condition each serves: gdelt_tv_stationchart for comparing stations, gdelt_tv_timeline for airtime over time, gdelt_tv_wordcloud for term frequencies. It also tells the agent exactly where to source the `stations` value.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.