Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gdelt_tv_stationchart

Compare US TV news coverage across stations by topic, returning counts per station based on transcript, caption, concept, visual, show, or time range.

Instructions

Compare US television news coverage across stations. Compares how much each US television station covered a topic. At least one station is required, and several are compared side by side. 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 each station with a count.

Input Schema

NameRequiredDescriptionDefault
toNoEnd of an absolute time window. Same formats as from.
fromNoStart of an absolute time window. Accepts YYYY-MM-DD, RFC3339, or GDELT's raw YYYYMMDDHHMMSS. Cannot be combined with timespan.
showNoLimit to an exact show name.
visualNoSearch visual object/activity labels from computer vision (GDELT's visual: operator). Repeatable; multiple values are OR'd together.
captionNoSearch human-provided closed captioning (GDELT's cap: operator). Repeatable; multiple values are OR'd together.
conceptNoSearch Google Knowledge Graph concepts extracted from captioning, by MID code (GDELT's capnlp: operator). Repeatable; multiple values are OR'd together.
stationYesRequired, repeatable. One or more stations, OR'd together.
timespanNoRelative 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).
transcriptNoSearch 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_textNoSearch 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_visualNoExclude clips whose visual labels match this value (GDELT's -visual: operator). Repeatable; every value must be absent.
exclude_captionNoExclude clips whose closed captioning matches this value (GDELT's -cap: operator). Repeatable; every value must be absent.
exclude_conceptNoExclude clips whose extracted concepts match this MID code (GDELT's -capnlp: operator). Repeatable; every value must be absent.
exclude_transcriptNoExclude clips whose speech-to-text transcript matches this value (GDELT's -asr: operator). Repeatable; every value must be absent.
exclude_onscreen_textNoExclude 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.

  1. Changed11 schema fields changedv1.17.5
    • 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"
+}
  2. Addedv1.16.0

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 usefully discloses that a match is built from one of several operators with exclude_ counterparts, optional show/timespan/from-to narrowing, and that the result is per-station counts. It does not disclose pagination, rate limits, auth needs, or archive-resolution behavior beyond what's implied.

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?

Front-loaded with the core operation and a follow-on clarifying sentence. Slightly redundant, as the first and second sentences restate the same idea, but overall tight and well-structured for a complex tool.

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, the description adequately covers the required parameter, the match-building operators, the optional narrowing inputs, and the shape of the result (each station with a count). It is complete enough to call correctly, with only minor gaps around behavioral limits.

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 thoroughly. The description restates the key ones (station required, the match operators, time filters) but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource: 'Compares how much each US television station covered a topic', which is a concrete analytic operation. It does not name or distinguish from the many GDELT siblings (gdelt_tv_showchart, gdelt_tv_timeline, gdelt_tv_search), so an agent must infer the boundary from context.

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 that 'at least one station is required' and that several are compared side by side, which implies the comparative use case. However, it offers no explicit when-to-use vs alternatives guidance against the sibling GDELT TV tools, leaving selection 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

Other Tools