Skip to main content
Glama

China News Search

china_news_search
Read-onlyIdempotent

Search recent news coverage from Chinese, Hong Kong, Taiwanese and overseas-Chinese publishers, Xinhua, China Daily, Global Times, People's Daily, South China Morning Post, CNA Taiwan, CGTN, Caixin and 20 more, by keyword, publisher, jurisdiction, language and date. Returns headline, publisher, URL, publication time, GDELT themes and average article tone for each match. Use it to see how mainland state media, Hong Kong and Taiwanese outlets are covering a topic, and how that differs. Article metadata only, from the GDELT Global Knowledge Graph: there is no article text, follow the url. Covers a rolling 30-day window. Call china_news_outlets to see exactly which publishers are searchable.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 5,
      "query": "Taiwan"
    },
    "name": "china_news_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoPublishing language of the edition the article appeared in: "zh" or "en". Note that most mainland state outlets run a separate English edition on its own host (english.news.cn, en.people.cn), and this filter reads that host, so lang:"en" does return Xinhua and People's Daily.
limitNoMax articles (1-100, default 25).
queryNoFree text, matched case-insensitively against the headline, the article URL and GDELT's theme tags, e.g. "Taiwan", "semiconductor", "BRICS". Omit to browse the most recent articles for the other filters.
sinceNoOnly articles published at or after this date, YYYY-MM-DD or an ISO timestamp.
untilNoOnly articles published at or before this date, YYYY-MM-DD or an ISO timestamp.
regionNoOne of: cn | hk | tw | overseasthe publisher's own jurisdiction (cn = mainland China, hk = Hong Kong, tw = Taiwan, overseas = diaspora/foreign Chinese-language outlets). This is NOT the language it publishes in; use lang for that.
outletsNoRestrict to specific publishers, a home domain ("news.cn", "scmp.com") or a publisher name ("South China Morning Post"). Comma-separated string or array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Publishing language of the edition the article appeared in: \"zh\" or \"en\". Note that most mainland state outlets run a separate English edition on its own host (english.news.cn, en.people.cn), and this filter reads that host — so lang:\"en\" does return Xinhua and People's Daily."New value: +"Publishing language of the edition the article appeared in: \"zh\" or \"en\". Note that most mainland state outlets run a separate English edition on its own host (english.news.cn, en.people.cn), and this filter reads that host, so lang:\"en\" does return Xinhua and People's Daily."
    • changedInput schema / properties / outlets / description
      Previous value: -"Restrict to specific publishers — a home domain (\"news.cn\", \"scmp.com\") or a publisher name (\"South China Morning Post\"). Comma-separated string or array."New value: +"Restrict to specific publishers, a home domain (\"news.cn\", \"scmp.com\") or a publisher name (\"South China Morning Post\"). Comma-separated string or array."
    • changedInput schema / properties / region / description
      Previous value: -"One of: cn | hk | tw | overseas — the publisher's own jurisdiction (cn = mainland China, hk = Hong Kong, tw = Taiwan, overseas = diaspora/foreign Chinese-language outlets). This is NOT the language it publishes in; use lang for that."New value: +"One of: cn | hk | tw | overseasthe publisher's own jurisdiction (cn = mainland China, hk = Hong Kong, tw = Taiwan, overseas = diaspora/foreign Chinese-language outlets). This is NOT the language it publishes in; use lang for that."
    • changedInput schema / properties / since / description
      Previous value: -"Only articles published at or after this date — YYYY-MM-DD or an ISO timestamp."New value: +"Only articles published at or after this date, YYYY-MM-DD or an ISO timestamp."
    • changedInput schema / properties / until / description
      Previous value: -"Only articles published at or before this date — YYYY-MM-DD or an ISO timestamp."New value: +"Only articles published at or before this date, YYYY-MM-DD or an ISO timestamp."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is settled; the description adds what annotations cannot: data provenance (GDELT Global Knowledge Graph), the metadata-only limitation with no article body, and a rolling 30-day coverage window. Those three facts materially change how an agent interprets empty or truncated results.

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?

Front-loaded with purpose, then filters, then return values, then the critical caveats (metadata only, 30-day window) — a sensible order. The publisher roll-call of eight named outlets plus "20 more" is longer than needed given china_news_outlets exists, but it does establish credibility of the source set, so the cost is modest.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 (headline, publisher, URL, publication time, GDELT themes, average tone). Combined with the coverage window, data source and the pointer to china_news_outlets, an agent has everything needed to call this and interpret results correctly.

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% and the schema already explains the lang/region distinction in detail, including the English-edition host subtlety. The description's phrase "by keyword, publisher, jurisdiction, language and date" merely restates the parameter set in prose without adding syntax, defaults or edge-case behavior. Baseline 3 is appropriate when the schema carries the semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Search recent news coverage") plus the exact publisher universe, the filter axes (keyword, publisher, jurisdiction, language, date) and the return fields. It also distinguishes itself from the sibling china_news_outlets by pointing there for the publisher list, so an agent can route correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete use case — comparing how mainland state media, Hong Kong and Taiwanese outlets cover the same topic — which is the clearest signal of when to pick this tool. It also names the china_news_outlets alternative for enumerating publishers. It stops short of explicit when-not-to-use guidance (e.g. naming china_news_article for full text) but the "follow the url" note covers that need functionally.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.