Crawlora MCP

gdelt_tv_search

Read-only

Search GDELT Television 2.0 coverage of US broadcasts using captions, OCR, transcripts, and visual labels. It covers four US stations and results may arrive 24–48 hours after airing; use gdelt-search or gdelt-context for global online news instead.

Input Schema

TableJSON 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.
`sort`	No	Result order. Allowed values: relevance (default), datedesc, dateasc.
`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. GDELT's TV archive starts July 6, 2010.
`maxrecords`	No	Rows to return, default 50, max 3000 (GDELT's own hard cap for this endpoint; there is no pagination cursor beyond this).
`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).
`day_of_week`	No	Limit to a day of week, 0 (Sunday) through 7 (Saturday), PST.
`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

TableJSON 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 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely useful operational context about the 24-48 hour ingestion lag. However, it also asserts 'four US stations' while the schema enumerates seven (CNN, MSNBC, FOXNEWS, BBCNEWS, KGO, KPIX, KNTV), an internal inconsistency that can mislead about coverage scope.

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 sentences, no hedging or filler. The capability statement comes first and the routing/alternative guidance follows, with every clause carrying distinct information.

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?

With an output schema present and a fully documented input schema, the description does not need to explain return values, and it does supply the two facts an agent most needs: the archive's freshness lag and the correct sibling for non-TV news. The station-count discrepancy is the only thing keeping it from being fully complete.

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% across all 18 parameters, including operator mappings (cap:, ocr:, asr:, visual:, -capnlp:), OR vs AND semantics, and the maxrecords hard cap. The description adds no parameter-level information beyond this, so baseline 3 applies.

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?

The first sentence gives a specific verb and resource ('Search GDELT Television 2.0 coverage of US broadcasts') and enumerates the media searched (captions, OCR, transcripts, visual labels). The second sentence explicitly names the sibling tools it is not (gdelt-search, gdelt-context), so an agent can route correctly 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 Guidelines4/5

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

It supplies a clear use condition and an explicit alternative: use gdelt-search or gdelt-context for global online news instead. What it omits is guidance against the other TV analytics siblings (gdelt_tv_timeline, gdelt_tv_showchart, gdelt_tv_wordcloud), which is a modest gap rather than a misleading one.

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.

Resources

Need Help?