Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

gdelt_tv_timeline

Track how much US TV news airtime matches a query over time. Choose a station and time range to get GDELT Television timeline-volume totals.

Instructions

Airtime volume over time for US television news coverage. Returns the amount of US television news airtime matching the supplied query over time, using GDELT Television 2.0 AI timeline-volume data. A station is required. Supports the same caption, transcript, concept, and visual match operators as gdelt-tv-search; coverage and processing-delay caveats are documented there.

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.
`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. 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.
`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.

Changed11 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 / 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/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns airtime volume over time, which conveys its basic behavior. It mentions 'coverage and processing-delay caveats are documented there' (in gdelt-tv-search), acknowledging that caveats exist but not disclosing them here. It does not describe the output format (e.g., time series granularity) or any limitations beyond requiring a station. While it gives some behavior, it is incomplete for a tool with no annotations.

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?

The description is two sentences, front-loaded with the core purpose and essential constraint. It wastes no words and includes a helpful pointer to a sibling for caveats. Each sentence earns its place.

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?

The tool has 15 parameters but all are well-documented in the schema. The description provides a high-level return description ('Returns the amount of ... airtime ... over time') which gives an idea of the output, though it does not specify exact format or granularity. It points to gdelt-tv-search for caveats, which addresses potential gaps. Given the schema richness and the description's clear purpose, it is reasonably complete, though it could detail the output structure.

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 coverage is 100% – every parameter has a description in the input schema. The description adds minimal value: it mentions 'A station is required' (already in schema as required) and states that it supports the same operators as gdelt-tv-search, which provides cross-reference context but not new semantics. Since the schema already documents parameter meanings, a baseline of 3 is appropriate.

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 clearly states the tool's function: 'Airtime volume over time for US television news coverage' and 'Returns the amount of US television news airtime matching the supplied query over time'. It specifies the verb (returns), the resource (airtime volume), and the scope (US TV news). It distinguishes from siblings by mentioning 'timeline-volume data' and referencing gdelt-tv-search for operators, making its unique purpose evident.

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?

The description provides key usage constraints: 'A station is required' and references gdelt-tv-search for caveats. It implies when to use (when timeline volume is needed) but does not explicitly state alternatives or exclusions. It does not mention that gdelt_tv_showchart or gdelt_tv_stationchart are for different purposes. Lacks an explicit 'use this instead of X' statement, but the reference to gdelt-tv-search for operators and caveats gives some context.

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_timeline

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools