Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

gdelt_tv_stationchart

Compare US television news coverage across specified stations using GDELT data. Return result-count comparisons by station, time window, show, or topic filters.

Instructions

Compare US television news coverage across stations. Return a result-count comparison across the requested.

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	Required, repeatable. One or more stations, OR'd together.
`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 / items
```
Added value: +{
+  "enum": [
+    "CNN",
+    "MSNBC",
+    "FOXNEWS",
+    "BBCNEWS",
+    "KGO",
+    "KPIX",
+    "KNTV"
+  ],
+  "type": "string"
+}
```
- addedInput schema / properties / transcript / items
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / visual / items
```
Added value: +{
+  "type": "string"
+}
```
Addedv1.16.0Aug 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the core function and output type, but does not mention how the result-count is aggregated, whether time windows are supported, any limitations on filtering, or the structure of the response. It also does not clarify that it requires at least one station, which is in the schema but not emphasized.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (two sentences), which is appropriate for conciseness, but the second sentence is grammatically incomplete ('across the requested.'). This detracts from clarity and structure. The first sentence is effective, but the dangling phrase undermines the overall quality.

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

Completeness3/5

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

Given the tool's complexity (15 parameters) and lack of output schema or annotations, the description is minimal. It does not explain the output format beyond 'result-count comparison', nor does it indicate that it aggregates per station or how to interpret the counts. The schema covers parameter details, but the description should at least clarify the return structure and any key constraints, which it does not.

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 already documents all 15 parameters. The description adds no parameter-specific meaning beyond what is in the schema, providing only a generic 'compare across stations' summary. This meets the baseline of 3 but does not enhance understanding of how parameters like timespan or transcript filters affect the comparison.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool compares US television news coverage across stations and returns a result-count comparison. This differentiates it from sibling tools like gdelt_tv_showchart (which compares by show) and gdelt_tv_timeline (which tracks over time). However, the phrase 'across the requested' is ambiguous—it likely means requested stations, but is not explicit.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. It does not mention gdelt_tv_showchart or gdelt_tv_stationdetails, nor does it specify that this is for station-level comparison while others handle different dimensions. An agent would have to infer the intended use case from the name and description alone, which is insufficient.

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_stationchart

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools