Overview
Theget_media_event_cluster tool provides a deep-dive into a single story cluster discovered via get_media_events. It returns the cluster’s top-ranked articles, common entities, resolved metrics, and supports filters to explore specific angles of the story.
Always pass the same
date and days values you used in get_media_events to ensure efficient queries.Parameters
The cluster ID to fetch. Obtained from a
get_media_events response.Anchor/end date in
YYYY-MM-DD format. Must match the date used in get_media_events. Defaults to today UTC.Lookback window in days. Must match the days used in get_media_events. Max 30.
Response detail level.
| Level | ~Tokens | Description |
|---|---|---|
summary | ~500 | Voting articles (URL, title, domain, date, geo) + top 10 common entities + resolved metrics |
standard | ~1,500 | Adds event metrics/actors to voting articles, top 5 entities per article, paginated additional articles |
full | ~3,000+ | All entities per voting article, top 10 entities per paginated article, quad_classes |
Number of additional articles beyond voting articles (standard/full only). Max 50.
Pagination offset for additional articles (standard/full only).
Filters
Use filters to explore specific angles of a story:ISO-3 country code to filter by actor nationality. Example:
CHN to see how China is involved.FIPS 2-letter code to filter by event location. Example:
IR for events in Iran.ISO 639-1 code to filter by article language. Example:
fr for French-language coverage.Filter to articles from a specific source domain. Example:
reuters.com.Response Shape
Summary (default)
Standard / Full
Addsarticles array (paginated additional articles beyond the top 5 voting articles), richer entity data per article, and pagination metadata (has_more, additional_total).
When filters are applied, the response includes filtered_count showing how many articles match.

