Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gdelt_search

Search continuously updated global news from the GDELT Project using queries with time windows, filters, and sorting to find relevant articles.

Instructions

Search global news coverage indexed by GDELT. Search the GDELT Project's continuously updated global news.

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; 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

C2.8/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states that it searches news, with no mention of read-only nature, rate limits, output format, or any limitations. The schema mentions the 3-month indexing window, but the description itself adds no behavioral context.

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

Conciseness3/5

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

The description is short (two sentences) but redundant—the second sentence essentially restates the first. It is not front-loaded with unique information. It is not verbose, but it wastes a sentence on repetition, making it adequate but not efficient.

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?

With 9 parameters, no output schema, and no annotations, the description should provide substantial context. It fails to explain what the results look like, how to interpret them, or any usage notes beyond the schema. The schema covers parameter details, but the description leaves the overall behavior and expected output completely unspecified, which is insufficient for a tool of this complexity.

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%: all 9 parameters have detailed descriptions in the schema itself. The tool description adds no additional parameter semantics beyond what the schema already provides. This is the baseline score when the schema does the heavy lifting.

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 clearly states the verb 'search' and the resource 'global news coverage indexed by GDELT', which is unambiguous. However, it repeats the same idea in both sentences and does not differentiate from sibling GDELT tools like gdelt_timeline or gdelt_tv_search, so it misses an opportunity to distinguish itself.

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 guidance on when to use this tool versus other GDELT tools. It does not mention any alternatives, exclusions, or prerequisites. An agent would have no idea that this is the primary search tool while gdelt_timeline or gdelt_tonechart serve different purposes.

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