Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

gdelt_tv_showchart

Rank US television shows by coverage share for a topic, using required station filters and optional show or time limits. Returns each show with a count.

Instructions

Top US television shows by coverage share for a query. Ranks US television shows by how much they covered a topic. At least one station is required, and a match is set with transcript, caption, concept, onscreen_text or visual (with exclude_ counterparts), optionally limited by show, timespan or from and to. Returns shows with a count. Omitting the time window searches the archive back to July 2010.

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

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does add real behavioral value: the default time window ('Omitting the time window searches the archive back to July 2010') and the return shape ('Returns shows with a count'). It stops short of confirming read-only semantics, rate limits, or error behavior, which is a gap for a 15-param tool.

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 ranking purpose and then the constraint/parameter summary. Every sentence carries information and nothing is padded, though the parameter enumeration sentence is dense.

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?

For a 15-parameter tool with no output schema and no annotations, the description covers the required param, the query operator families, the optional limiters, and the default time window, plus the 'count' return. That is close to complete; only alternative-routing guidance is missing.

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 each operator fully, and the baseline is 3. The description reinforces the required station, the match-set operators and their exclude_ counterparts, and the timespan/from-to exclusivity, but adds little syntax or format detail beyond the schema.

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 gives a specific verb+resource ('Ranks US television shows by how much they covered a topic') and states the ranking metric (coverage share). It is clear what the tool produces, though it never explicitly contrasts itself with the sibling gdelt_tv_stationchart, so an agent must infer the show-vs-station distinction.

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 states the hard requirement ('At least one station is required') and the query mechanics, which is useful context. However, it never says when to pick this over siblings like gdelt_tv_stationchart, gdelt_tv_timeline, or gdelt_tv_search, so alternative selection is left to inference.

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_showchart

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools