Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gdelt_tv_showchart

Discover top US TV shows by coverage share for any query. Returns shows ranked by result percentage to identify which programs dominate news coverage.

Instructions

Top US television shows by coverage share for a query. Return the top shows by result percentage for a query.

Input Schema

TableJSON 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

B3.1/5.0
Behavior2/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 does not explain what 'coverage share' or 'result percentage' mean, does not mention that station is required (though schema does), does not describe the output format or any limitations such as the US-only scope or the need for a query. This is a significant gap for a tool with no annotation support.

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?

The description is two sentences and very short, but it repeats the same idea twice ('Top US television shows by coverage share' and 'Return the top shows by result percentage'), which is slightly redundant. It is efficient but could be trimmed to one sentence without losing meaning.

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

Completeness2/5

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

For a tool with 15 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the meaning of 'coverage share', does not clarify how the required station parameter works with the query, does not describe the return structure, and gives no guidance on using the many filter parameters. An agent would struggle to use this correctly based on the description alone.

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 every parameter already has a description in the schema. The tool description adds no additional meaning beyond what the schema provides, such as how query and station interact or how the many filter parameters affect results. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 states it returns top US television shows by coverage share/result percentage for a query, which is a clear verb+resource. It distinguishes itself from other GDELT tools by focusing on shows, but it does not explicitly name alternatives like gdelt_tv_stationchart or gdelt_tv_timeline, so differentiation is implicit rather than explicit.

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?

The phrase 'for a query' implies the tool is used when you want top shows for a specific query, but there is no explicit guidance on when to use this versus sibling GDELT TV tools, nor any exclusions or alternatives mentioned. The usage context is implied but not stated.

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