Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

gdelt_tv_timeline

Measure US television news airtime volume over time. Filter by station, show, captions, or concepts to see how much coverage a topic receives.

Instructions

Airtime volume over time for US television news coverage. Return how much airtime a query's matching US television.

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.
stationYesStation to search.
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.
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It only says the tool returns airtime volume over time, but doesn't state units, what 'matching' means, how time windows behave beyond the schema, or whether this is a read-only operation. The incomplete sentence leaves the actual behavior ambiguous.

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

Conciseness2/5

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

The description is short, but the second sentence is a broken fragment that obscures rather than clarifies. It's under-specified rather than cleanly concise, and the structure fails to deliver a complete thought.

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?

This is a complex tool with 15 parameters and no output schema, yet the description does not explain how to specify a query (station, concept, caption, etc.), what 'airtime volume' means, or what the response format looks like. The description is far too sparse to support correct invocation without deep schema inspection.

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 input schema already documents all 15 parameters. The tool description adds no parameter-level meaning beyond what the schema provides, keeping this at the baseline score for high coverage.

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

Purpose3/5

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

The first sentence identifies the resource ('airtime volume over time for US television news coverage'), which gives a general sense of the tool. However, the second sentence is grammatically incomplete and confusing ('a query's matching US television'), leaving the exact object of the query unclear. It also doesn't distinguish this from sibling tools like gdelt_tv_showchart or gdelt_tv_stationchart.

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?

There is no guidance on when to use this tool versus the many sibling GDELT tools (e.g., gdelt_tv_search, gdelt_tv_tonechart). The description doesn't mention query construction, required parameters, or alternatives, so an agent must infer usage entirely from the schema.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server