GDELT DOC Search
Use the CLI-owned gdelt.doc-search capability. This Skill supplies intent
routing and result-use boundaries only; the CLI owns source discovery,
input/output schemas, HTTP behavior, limits, validation, and receipts.
Before running
- Read
references/tiangong-data-requirement.json.
- Use the caller- or workspace-resolved stable CLI. The requirement declares
compatible capability and operation contract majors; it does not select a
package build.
- Run
data describe with that same CLI. Continue only when the capability
ID and required contract majors match, and copy the exact current
capability/operation versions from that response into the run request.
- Immediately inspect
manifest.availability and discovery.availability.
If either does not report available, stop before constructing a request
and report its exact reasonCode, description, and resume criteria. Do not
bypass suspension with a direct provider request. Route to GDELT Web NGrams
only when the caller accepts its different literal phrase-search semantics.
tiangong-ai data describe gdelt.doc-search --json
Use the returned Discovery Metadata to confirm current source coverage,
freshness, restrictions, provides, and doesNotProvide. Do not substitute
facts remembered from an older Skill revision.
Prepare the request
Build a tiangong.data.run-request.v1 envelope. Replace the two version
placeholders with the exact versions from the same data describe response. This example requests an
article list for one bounded absolute UTC window:
{
"schemaVersion": "tiangong.data.run-request.v1",
"capabilityId": "gdelt.doc-search",
"capabilityVersion": "<describe.manifest.capabilityVersion>",
"operationId": "search",
"operationVersion": "<describe.manifest.operations[0].operationVersion>",
"input": {
"query": "(\"climate change\" OR pollution) sourcecountry:us",
"mode": "artlist",
"absoluteWindow": {
"from": "2026-03-01T00:00:00Z",
"to": "2026-03-07T23:59:59Z"
},
"maxRecords": 75,
"sort": "hybridrel"
}
}
Use the operation input schema returned by the same data describe response to select a
supported mode and its mode-specific fields. Use at most one time-window form;
omitting both uses the provider default window. Never silently widen a supplied
window or pass arbitrary DOC parameters absent from the schema.
The CLI lints every effective query before network access. Wrap boolean OR
groups in parentheses and use exactDomains (domainis:) or domains
(domain:), never site: or inurl:. Repeated domains become separate
bounded batches. Set continueOnQueryError only when a partial merged result is
useful and retain batchQueries plus queryErrors.
Run
tiangong-ai data run gdelt.doc-search search \
--input /absolute/path/to/request.json --json
The command emits a tiangong.data.run-result.v1 envelope. Preserve its
contract, warnings, errors, and receipt with data when handing the
result to another workflow.
Result boundaries
- Persistent DOC throttling is unavailable retrieval, not zero coverage. When
literal topic discovery fits the task, consider the separately described
gdelt-web-ngrams-search Skill as an explicit change of retrieval method.
It does not support DOC operators or reproduce DOC aggregate timelines.
- Treat article-list results as source metadata and links, not downloaded
article bodies, verified claims, or independent evidence units.
- Treat timelines, tone, language, and source-country outputs as automated
aggregates whose meaning depends on the selected mode; do not compare unlike
measures or infer causality from them.
- In
tonechart, articleCount is the count assigned to a tone bin, not the
tone score itself and not a public-sentiment estimate.
- GDELT source coverage and automated extraction can be uneven. Do not treat
counts, tone, or rankings as representative measurements of public opinion,
media prevalence, event truth, or sentiment ground truth.
- Surface
partial, truncation warnings, and empty results. Never reinterpret
them as complete absence of coverage.
- Use a dedicated GDELT Events, GKG, or Mentions Skill when structured feed rows
are required: GKG supplies document annotations, Events supplies coded events,
and Mentions links events to documents. This Skill must not invoke or combine
them automatically, and their statistics are not interchangeable with DOC.
- Cross-source comparison, full-text acquisition, persistence, polling, and
research evidence admission belong to the caller or Auto Research.
Reference
references/tiangong-data-requirement.json: stable capability requirement; it is not a package lock.
1---2name: gdelt-doc-search3description: Search GDELT DOC 2.0 through the Tiangong CLI for bounded article metadata, timeline aggregates, or tone-distribution bins using linted GDELT query syntax and optional split domain filters. Use for news-source discovery and trend reconnaissance; do not use for article bodies, raw GDELT event/GKG/mention rows, representative media measurement, fact verification, sentiment ground truth, or causal inference.4---5
6# GDELT DOC Search
7
8Use the CLI-owned `gdelt.doc-search` capability. This Skill supplies intent
9routing and result-use boundaries only; the CLI owns source discovery,
10input/output schemas, HTTP behavior, limits, validation, and receipts.
11
12## Before running
13
141. Read `references/tiangong-data-requirement.json`.
152. Use the caller- or workspace-resolved stable CLI. The requirement declares
16 compatible capability and operation contract majors; it does not select a
17 package build.
183. Run `data describe` with that same CLI. Continue only when the capability
19 ID and required contract majors match, and copy the exact current
20 capability/operation versions from that response into the run request.
214. Immediately inspect `manifest.availability` and `discovery.availability`.
22 If either does not report `available`, stop before constructing a request
23 and report its exact `reasonCode`, description, and resume criteria. Do not
24 bypass suspension with a direct provider request. Route to GDELT Web NGrams
25 only when the caller accepts its different literal phrase-search semantics.
26
27```bash
28tiangong-ai data describe gdelt.doc-search --json
29```
30
31Use the returned Discovery Metadata to confirm current source coverage,
32freshness, restrictions, `provides`, and `doesNotProvide`. Do not substitute
33facts remembered from an older Skill revision.
34
35## Prepare the request
36
37Build a `tiangong.data.run-request.v1` envelope. Replace the two version
38placeholders with the exact versions from the same `data describe` response. This example requests an
39article list for one bounded absolute UTC window:
40
41```json
42{
43 "schemaVersion": "tiangong.data.run-request.v1",
44 "capabilityId": "gdelt.doc-search",
45 "capabilityVersion": "<describe.manifest.capabilityVersion>",
46 "operationId": "search",
47 "operationVersion": "<describe.manifest.operations[0].operationVersion>",
48 "input": {
49 "query": "(\"climate change\" OR pollution) sourcecountry:us",
50 "mode": "artlist",
51 "absoluteWindow": {
52 "from": "2026-03-01T00:00:00Z",
53 "to": "2026-03-07T23:59:59Z"
54 },
55 "maxRecords": 75,
56 "sort": "hybridrel"
57 }
58}
59```
60
61Use the operation input schema returned by the same `data describe` response to select a
62supported mode and its mode-specific fields. Use at most one time-window form;
63omitting both uses the provider default window. Never silently widen a supplied
64window or pass arbitrary DOC parameters absent from the schema.
65
66The CLI lints every effective query before network access. Wrap boolean `OR`
67groups in parentheses and use `exactDomains` (`domainis:`) or `domains`
68(`domain:`), never `site:` or `inurl:`. Repeated domains become separate
69bounded batches. Set `continueOnQueryError` only when a partial merged result is
70useful and retain `batchQueries` plus `queryErrors`.
71
72## Run
73
74```bash
75tiangong-ai data run gdelt.doc-search search \
76 --input /absolute/path/to/request.json --json
77```
78
79The command emits a `tiangong.data.run-result.v1` envelope. Preserve its
80`contract`, `warnings`, `errors`, and `receipt` with `data` when handing the
81result to another workflow.
82
83## Result boundaries
84
85- Persistent DOC throttling is unavailable retrieval, not zero coverage. When
86 literal topic discovery fits the task, consider the separately described
87 `gdelt-web-ngrams-search` Skill as an explicit change of retrieval method.
88 It does not support DOC operators or reproduce DOC aggregate timelines.
89- Treat article-list results as source metadata and links, not downloaded
90 article bodies, verified claims, or independent evidence units.
91- Treat timelines, tone, language, and source-country outputs as automated
92 aggregates whose meaning depends on the selected mode; do not compare unlike
93 measures or infer causality from them.
94- In `tonechart`, `articleCount` is the count assigned to a tone bin, not the
95 tone score itself and not a public-sentiment estimate.
96- GDELT source coverage and automated extraction can be uneven. Do not treat
97 counts, tone, or rankings as representative measurements of public opinion,
98 media prevalence, event truth, or sentiment ground truth.
99- Surface `partial`, truncation warnings, and empty results. Never reinterpret
100 them as complete absence of coverage.
101- Use a dedicated GDELT Events, GKG, or Mentions Skill when structured feed rows
102 are required: GKG supplies document annotations, Events supplies coded events,
103 and Mentions links events to documents. This Skill must not invoke or combine
104 them automatically, and their statistics are not interchangeable with DOC.
105- Cross-source comparison, full-text acquisition, persistence, polling, and
106 research evidence admission belong to the caller or Auto Research.
107
108## Reference
109
110- `references/tiangong-data-requirement.json`: stable capability requirement; it is not a package lock.