Crawlora MCP

gdelt_tv_timeline

Read-only

Return time-bucketed US TV airtime-volume series for a required station from gdelt_tv_stationdetails, using GDELT TV 2.0 caption/transcript/concept/OCR/visual filters. Relative timespan and absolute dates cannot be combined; coverage may lag broadcasts by 24-48 hours. Use gdelt_tv_stationchart for station comparisons or gdelt_timeline for global web coverage.

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.
`station`	Yes	Required. Station to search. 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.

First observedOct 7, 2026

TDQS

A4.3/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 new behavioral context: a 24-48 hour coverage lag and the timespan/absolute-date incompatibility. Return format and bucketing granularity are left to the output schema.

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?

Three sentences, front-loaded with the core purpose, then the constraint, then the disambiguation. Efficient, though the filter enumeration ('caption/transcript/concept/OCR/visual') slightly duplicates schema detail.

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?

Given a rich 15-param schema with full coverage, an output schema, and read-only annotations, the description carries the remaining burden well: latency caveat, time-window exclusivity, and sibling routing. Completeness is strong for this complexity level.

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 schema fully documents all 15 parameters including filter operators. The description only restates the required `station` and the timespan/from exclusion already stated in the schema, adding little beyond it.

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 ('Return'), precise resource ('time-bucketed US TV airtime-volume series'), and scope ('US TV', required `station`). It also names sibling tools it is not (gdelt_tv_stationchart, gdelt_timeline), so an agent can distinguish it without opening a schema.

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?

Explicitly routes to alternatives with conditions: gdelt_tv_stationchart for station comparisons, gdelt_timeline for global web coverage. It also flags the timespan-vs-from mutual exclusivity, so the agent knows the valid invocation modes.

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.