Overview
Thegdelt_cloud_* MCP wrappers expose the public API v2 product catalog:
- structured Events:
conflictandcameoplus - clustered Stories with article evidence
- Event and Story summaries
- Entities linked to Events and Stories
- country-scoped
admin1discovery - Facilities — the unified physical-asset directory (
facilities_search,facilities_get,facilities_by_owner; plan-gated, Analyst+) - Monitoring Briefs —
create_brief,list_briefs,get_brief(plan-gated; see Monitoring Briefs)
region and continent expand to ISO-3 country lists on the API backend. Event tools match those countries against Event location plus actor-origin countries. Story tools use the same country-list expansion through linked Event primary location only.
Event, Story, and Entity list tools default to the exact past 24 hours. Narrow with geography, category, subcategory, civilian-targeting filters, date windows up to 30 days, and semantic search rather than public confidence modes. subcategory requires its parent category. Detail tools (get_event, get_story, and Story articles) resolve known IDs directly.
List and detail tools preserve API-enriched visual context by default: top source-article sharing images, source-domain avatars, and linked Entity thumbnails when available. These fields are for product rendering and analyst orientation; absence of an image is not evidence about the underlying Event, Story, or Entity.
Wrapper Parameters
Shared Date Parameters
Range-capable tools acceptstart_date, end_date, and days.
Precedence:
start_date+end_date: use the explicit inclusive range.start_date+days: computeend_date.end_date+days: computestart_date.daysonly: trailing window ending current UTC date. On list tools, the defaultdays=1returns the exact past 24 hours.
search_events
Use for incident-level structured records: protests, attacks, diplomatic actions, infrastructure projects, economic policy events, and other coded Events.
summarize_events
Use for dashboards and trend charts before drilling into records. Summary tools do not accept search; use search_events first for semantic retrieval, then summarize with structured filters.
For time-series plots, call with group_by=date across a meaningful recent window such as days=14 or days=30. Each returned bucket is one chronological observation with count fields plus metric aggregates such as Goldstein, magnitude, systemic importance, propagation potential, market sensitivity, significance, confidence, articles, and fatalities.
Use gdelt_cloud_tool_get(tool_name="search_events", category="TECHNOLOGY") to retrieve the scoped subcategory enum before calling. Use group_by=subcategory when you want observed live buckets and counts after choosing a parent category. For example, summarize_events(category="Battles", group_by="subcategory") returns ACLED sub-event buckets such as Government regains territory; then call search_events(category="Battles", subcategory="Government regains territory") for the underlying Event cards.
Metric filters apply before aggregation. significance and confidence apply across Event families; CAMEO+ detail filters only match scored CAMEO+ Events; Goldstein filters match Conflict and CAMEO+ POLITICAL Events. goldstein_severity is absolute intensity, not signed valence.
get_event
search_stories
Use for narrative clusters, article evidence, and story-first questions.
summarize_stories
Use for dashboards and coverage trends before drilling into Story records. Summary tools do not accept search; use search_stories first for semantic retrieval, then summarize with structured filters.
For trend plots and Brief benchmark panels, call with group_by=date across a recent history window. Story summaries expose story/article counts and linked-Event metric aggregates; they should not be confused with distinct Event totals.
For group_by=category and group_by=subcategory, Story summary buckets use linked Event taxonomy. That makes them useful for coverage rollups such as category="Battles", group_by="subcategory" while preserving broad narrative coverage for date/geography summaries.
get_story
get_story_articles
search_entities
get_entity
list_admin1
Energy Data Tools
Use Energy tools for Global Energy Monitor registry questions: capacity, status, asset location, ownership, parent entities, and cross-tracker owner portfolios. Energy registry facts are structural; pair them with Events or Stories only when the user asks how current developments affect physical infrastructure.energy_search_owners
Resolve a company, ministry, state owner, person, or investment vehicle to a canonical GEM Entity ID before portfolio analysis.
energy_get_owner
Fetch one GEM ownership entity by entity_id, including registration/headquarters metadata, parent GEM entities, external IDs, source metadata, and a portfolio summary across energy assets.
energy_assets_by_owner
Pivot from a GEM Entity ID to every asset where that entity appears in owners, operators, or parents arrays.
Facilities Data Tools
Use Facilities tools for the unified physical-asset directory — GEM energy assets, World Port Index ports, and Epoch AI data centers on one keyed surface, each resolved to its owner entities on the spine. Answer “what facilities of type X exist in country Y”, “what does operator Z own”, or “which facilities sit near this event” (bbox / near). Plan-gated: the underlying/api/v2/facilities routes require the can_use_facilities entitlement (Analyst plan and up) and otherwise return 403 PLAN_REQUIRED.
facilities_search
Search the directory by name, type/class, source silo, geography, owner, status, and capacity.
facilities_get
Fetch one facility by its stable facility_id, including source attributes, owners (with spine entity_ids), and reversible cross-silo merge history.
facilities_by_owner
Pivot from a spine entity_id to every facility that entity owns across all silos — the owner → portfolio join.
Monitoring Briefs
A Monitoring Brief is a short, source-backed memo answering What changed? Why does it matter? What evidence supports it? What should I watch next? — quantified against a baseline and grounded in clickable GDELT Cloud evidence.Brief tools are plan-gated.
create_brief, list_briefs, and get_brief require a plan with Briefs access (can_use_briefs). On a plan without it these tools are hidden from the tool list and any call returns a BRIEF_ACCESS_DENIED error; once a plan’s included Brief runs are used up, create_brief returns BRIEF_LIMIT_REACHED. Brief runs are metered separately and do not consume the plan’s query-unit quota.create_brief
Create and kick off a Monitoring Brief. Non-blocking — returns immediately while the agent runs (~5–10 minutes); poll get_brief(brief_id) for status and content.
id, status (queued), title, and report URLs.
list_briefs
List the caller’s Monitoring Briefs with status and basic metadata (id, title, status, created_at, report URLs). No parameters.
get_brief
Fetch one Brief: status, the structured JSON document, citations, the evidence appendix, and report URLs.
Statuses progress
queued → generating → building → ready (or failed).
Response Objects
gdelt_cloud_tool_call returns an MCP call result whose structured content is the same REST-shaped response object returned by the selected v2 API endpoint. List tools return success, data, and pagination; detail tools return one data object; summary tools return group_by and summary buckets.
Event card
Returned bysearch_events and get_event.
Story card
Returned bysearch_stories and get_story.
Event summary bucket
Returned bysummarize_events.
Story summary bucket
Returned bysummarize_stories.
Articles, Entities, Admin1, And Standard error
get_story_articles returns Article objects with id, url, title, domain, article_date, rank, and role, plus pagination. search_entities returns Entity cards with id, url, name, type, wikipedia_url, and metrics. get_entity adds story_refs, event_refs, and admin-gated entity_tone when requested by API clients. list_admin1 returns success, normalized country, an admin1 array, and source.
Energy owner tools return GEM ownership records with entity_id, name, registration/headquarters fields, parent IDs, external IDs, portfolio_url, detail_url, and portfolio_summary. energy_get_owner(include_exposure=true) can also include admin-gated exposure summaries.
accepted_values, nearest_values when practical, and a corrected example so agents can recover in the next call. A subcategory without its parent category returns a compact parent-required error.
Output Notes
- Country output is plain English.
- Geo output includes
country,region,continent,admin1,location,latitude, andlongitudewhen available. - Event geography filters match location country or actor-origin country. Dashboard clients should compare
geo.location_countryandgeo_context.actor_origin_countriesto label a result as a location match, actor match, or both. - Event and Story cards include top 3 inline articles.
- Full Story article lists are paginated through
get_story_articles. metrics.goldstein_scaleis the only public Goldstein metric on Event cards. It is present for Conflict Events and CAMEO+POLITICALEvents where meaningful, and null for non-political CAMEO+ Events.- CAMEO+ detail metric filters (
magnitude,systemic_importance,propagation_potential,market_sensitivity) only match scored CAMEO+ Events.significanceandconfidenceare cross-family filters. - Those four are rubric scores — the coder reads concrete sub-factors off the source text and a fixed published formula turns them into the value. Read them as ordinal ranking signals, not measurements, probabilities, or predicted price moves.
magnitudeis comparable within a domain only and isnullwhen no severity observable was found (nullmeans unknown, never0). - Event significance is a family-scoped weighted blend, renormalized so every family spans a true 0–1: each event’s raw total is divided by the maximum its own family can reach (Conflict
1.00, CAMEO+POLITICAL0.90, other CAMEO+ domains0.65). All events: Goldstein severity0.25, article evidence0.05, confidence0.05. Conflict only: fatalities0.55(log-scaled by body count, saturating around 100 deaths), civilian targeting0.10. CAMEO+ only: magnitude0.20, systemic importance0.15, propagation potential0.10, market sensitivity0.10. Whenmagnitudeis unmeasured, both its term and its0.20weight are dropped. - Default ranking is canonical
significance; userecentwhen freshness matters more than importance.

