Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

gdelt_tv_search

Search GDELT's US TV news index by station for transcripts, captions, onscreen text, concepts, or visual labels, returning matching clips with show and URL.

Instructions

Search US television news coverage (transcripts, captions, OCR, visual labels). Searches GDELT's US television news index on one required station (CNN, MSNBC, FOXNEWS, BBCNEWS, KGO, KPIX or KNTV). Match on transcript, caption, concept, onscreen_text or visual, with matching exclude_ options. Returns up to maxrecords clips (default 50, max 3000) with show, station, timing, caption, transcript, onscreen text and clip URL. Results lag 24 to 48 hours.

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.
`sort`	No	Result order.
`visual`	No	Search visual object/activity labels from computer vision (GDELT's visual: operator). 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). Repeatable; multiple values are OR'd together.
`station`	Yes	Station to search.
`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. GDELT's own hard cap is 3000 for this endpoint; there is no pagination cursor beyond it.
`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.
`exclude_caption`	No	Exclude clips whose closed captioning matches this value (GDELT's -cap: operator). Repeatable; every value must be absent.
`exclude_concept`	No	Exclude clips whose extracted concepts match this MID code (GDELT's -capnlp: operator). Repeatable; every value must be absent.
`exclude_transcript`	No	Exclude clips whose speech-to-text transcript matches this value (GDELT's -asr: operator). Repeatable; every value must be absent.
`exclude_onscreen_text`	No	Exclude clips whose OCR'd onscreen text matches this value (GDELT's -ocr: operator). Repeatable; every value must be absent.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.17.5Sep 26, 2026
- addedInput schema / properties / caption / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / concept / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / exclude_caption / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / exclude_concept / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / exclude_onscreen_text / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / exclude_transcript / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / exclude_visual / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / onscreen_text / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / sort / enum
```
Added value: +[
+  "relevance",
+  "datedesc",
+  "dateasc"
+]
```
- addedInput schema / properties / station / enum
```
Added value: +[
+  "CNN",
+  "MSNBC",
+  "FOXNEWS",
+  "BBCNEWS",
+  "KGO",
+  "KPIX",
+  "KNTV"
+]
```
- addedInput schema / properties / transcript / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / visual / items
```
Added value: +{
+  "type": "string"
+}
```
Addedv1.16.0Aug 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the 24-48 hour result lag, the default/ceiling of maxrecords, and the hard station requirement. It stops short of describing permission or rate-limit behavior, but the key operational caveats are present.

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?

Four sentences, front-loaded with the core purpose and scope, then parameters, then output fields and the latency caveat. It is dense but each sentence carries distinct information; 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?

With no output schema, the description fills the gap by listing returned fields (show, station, timing, caption, transcript, onscreen text, clip URL). Combined with the station requirement and latency note, an agent has everything needed to call it correctly.

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, but the description adds meaning beyond the schema: it clarifies the matching fields operate as OR'd groups with paired `exclude_` counterparts and states the maxrecords default (50) that the schema omits.

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 description opens with a specific verb and resource ('Search US television news coverage') and enumerates exactly what is searchable (transcripts, captions, OCR, visual labels). It also names the exact index and required parameter, making it clearly distinguishable from siblings like gdelt_search and the gdelt_tv_* chart/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 Guidelines3/5

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

It gives operational context (one required `station`, match vs `exclude_` operators, maxrecords behavior) but never states when to prefer this tool over alternatives such as gdelt_search or the other gdelt_tv_* endpoints. Usage is implied rather than routed.

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

Deploy Server

gdelt_tv_search

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools