Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gdelt_context

Search the last 72 hours of GDELT news for sentences where every query term appears together, returning sentence, context, title, URL, domain, language, and quote flag.

Instructions

Sentence-level co-occurrence search across recent GDELT coverage. Searches the last 72 hours of GDELT-monitored news for sentences where every term of the required query appears together. Returns up to maxrecords rows (default 75, max 200), each with the matching sentence, its surrounding context, title, URL, domain, language and an is_quote flag. Filter with domain, language, is_quote, timespan or from and to, and order with sort.

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; GDELT caps this endpoint's window at 72 hours.
sortNoResult order.
queryYesGDELT query string. All terms must co-occur in the same sentence. Supports quoted phrases, (a OR b), domain:example.com.
domainNoConvenience domain filter, appended to the query as domain:VALUE.
is_quoteNoOnly return sentences GDELT identified as a quotation.
languageNoSource-language filter (GDELT's searchlang parameter). Space-segmented languages only (excludes CJK and similar).
timespanNoRelative time window ending now, e.g. 30min, 6h, 3d. Cannot be combined with from/to. GDELT caps this endpoint's window at 72 hours.
maxrecordsNoRows to return. GDELT's own hard cap is 200 for this endpoint (lower than gdelt-search's 250); there is no pagination cursor beyond it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "datedesc",
+  "dateasc"
+]
  2. Addedv1.16.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningfully: it discloses the 72-hour window, the absence of pagination beyond the 200-row cap, the default of 75 records, and the full shape of returned rows (sentence, context, title, URL, domain, language, is_quote). It omits any note on auth or rate limits, which keeps it short of a 5.

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 in a clear progression: purpose, search mechanism, return shape, then filters and ordering. Front-loaded and waste-free, though the return-field enumeration is the longest clause and could be trimmed without losing meaning.

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?

No output schema exists, and the description compensates by enumerating the returned fields and the row cap, plus the 72-hour ceiling that constrains every time parameter. An agent has enough to call it correctly; only the lack of any statement about result ordering semantics or failure modes keeps it from 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds value the schema lacks: the default maxrecords of 75 and the 200-row hard cap with no pagination cursor. It also restates the filter/sort surface coherently, though it doesn't explain the from/to vs timespan tradeoff beyond what the schema already documents.

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: 'sentence-level co-occurrence search across recent GDELT coverage', and spells out the mechanism (all terms must appear in the same sentence). It distinguishes itself from article-level siblings by emphasizing sentence granularity, but never names gdelt_search or gdelt_timeline, so the differentiation is inferential 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?

Usage is implied by the description's scope (72-hour window, sentence-level co-occurrence), which tells an agent roughly when it applies. However, it never states when to prefer this over gdelt_search or the timeline/tonechart siblings, and gives no exclusions or prerequisites. Adequate but leaves routing 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