Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gdelt_search

Search global news coverage indexed by GDELT using queries and operators; filter results by country, language, domain, and time window to retrieve matching articles.

Instructions

Search global news coverage indexed by GDELT. Searches global news coverage indexed by GDELT for the required query, which accepts quoted phrases, (a OR b), theme:, tone<N and domain:. Narrow with country, language, domain, and timespan or from and to (about the last 3 months are indexed). Returns up to maxrecords articles (default 75, max 250) with title, URL, domain, language, source country and seen_at.

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 only indexes roughly the last 3 months.
sortNoResult order.
queryYesGDELT query string. Supports GDELT's own search operators: quoted phrases, (a OR b), theme:NAME, tone<N / tone>N, near20:\
domainNoConvenience domain filter, appended to the query as domain:VALUE.
countryNoConvenience source-country filter, appended to the query as sourcecountry:VALUE. Accepts a GDELT-recognized country name (no spaces) or 2-letter FIPS code.
languageNoConvenience source-language filter, appended to the query as sourcelang:VALUE. Accepts a GDELT-recognized language name or 3-letter code.
timespanNoRelative time window ending now, e.g. 1h, 2d, 1w, 3m. Cannot be combined with from/to.
maxrecordsNoRows to return. GDELT's own hard cap is 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",
+  "tonedesc",
+  "toneasc"
+]
  2. Addedv1.16.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load and does so reasonably well: it discloses the ~3-month index coverage limit, the maxrecords hard cap of 250, and the absence of pagination beyond it, plus the exact fields returned. It omits auth/permission needs and rate limits, but the mutation/coverage constraints an agent most needs are present.

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?

Dense and front-loaded, packing operators, filter guidance, time constraints, and return shape into three sentences. The only waste is the near-duplicate opening ('Search global news coverage indexed by GDELT' followed immediately by 'Searches global news coverage indexed by GDELT for the required query').

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?

With no output schema, the description correctly compensates by listing the returned fields (title, URL, domain, language, source country, seen_at). Combined with the index-window and cap disclosures, an agent has nearly everything needed; only permission/auth context is absent.

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 description coverage is 100%, so the schema already documents all 9 parameters and a baseline of 3 applies. The description earns the extra point by surfacing the maxrecords default (75) that the schema omits and by enumerating the query operator vocabulary, adding meaning beyond the structured fields.

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 (search) and resource (global news coverage indexed by GDELT), which cleanly separates it from GDELT siblings like gdelt_timeline, gdelt_tonechart, and gdelt_context that analyze the same corpus differently. However, it never names those alternatives, so the 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?

It gives concrete narrowing guidance ('Narrow with country, language, domain, and timespan or from and to') and flags the ~3-month index window, which is real usage context. But it never says when to reach for this tool over the other GDELT tools (timeline, tonechart, context, tv_search), leaving the sibling-selection decision 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