Skip to main content
Glama

Crawlora MCP

gdelt_tv_timeline

Read-only

Airtime volume over time for US television news coverage via GDELT's Television 2.0 AI API.

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), e.g. VOLCANO, POLICE. 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), e.g. /M/0d063v. Repeatable -- multiple values are OR'd together.
stationYesRequired. Station to search. Allowed values: CNN, MSNBC, FOXNEWS, BBCNEWS, KGO (ABC San Francisco), KPIX (CBS San Francisco), KNTV (NBC San Francisco). See gdelt-tv-stationdetails for GDELT's own current list.
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 (AND'd exclusions).
exclude_captionNoExclude clips whose closed captioning matches this value (GDELT's -cap: operator). Repeatable; every value must be absent (AND'd exclusions).
exclude_conceptNoExclude clips whose extracted concepts match this MID code (GDELT's -capnlp: operator). Repeatable; every value must be absent (AND'd exclusions).
exclude_transcriptNoExclude clips whose speech-to-text transcript matches this value (GDELT's -asr: operator). Repeatable; every value must be absent (AND'd exclusions).
exclude_onscreen_textNoExclude clips whose OCR'd onscreen text matches this value (GDELT's -ocr: operator). Repeatable; every value must be absent (AND'd exclusions).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and external-data profile. The description adds that the tool computes airtime volume over time, which is a behavioral output trait, but it gives no operational details such as rate limits, aggregation semantics, or timezone handling.

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 a single front-loaded sentence with no wasted words. It is appropriately concise, though its extreme brevity for a 15-parameter tool slightly limits its standalone helpfulness.

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 rich schema (100% coverage), an output schema, and safety annotations, the description need not explain parameters or return values. However, for a complex TV search tool, it lacks usage guidance and sibling differentiation, leaving clear contextual gaps for an agent selecting among many GDELT TV endpoints.

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% for all 15 parameters, so the schema fully documents parameter meaning. The description adds no parameter-level guidance, which is acceptable at baseline 3 when the schema carries the burden.

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 a specific output metric ('Airtime volume over time') and a clear scope ('US television news coverage via GDELT's Television 2.0 AI API'). It is clear what the tool produces, but it does not distinguish this tool from siblings like gdelt_tv_stationchart or gdelt_timeline.

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?

The description gives no indication of when to use this tool versus alternatives, no exclusions, and no prerequisites. It only states the output, leaving the agent to infer usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources