List Google Trends trending searches
google_trends_trending_listFetch trending Google searches by country or region, then filter by time window, category, activity status, and sort order.
Instructions
List the searches trending on Google Trends by place. Optional inputs: geo, hours, category, active, sort and 2 more. Returns a list (use cursor when paginated).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "google_trends_trending_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| geo | No | Place: an ISO 3166-1 country code (`US`, `DE`) or a subdivision code (`US-CA`, `DE-BY`). Lowercase input is accepted and normalised to uppercase. Default: `US`. | US |
| sort | No | How to order the list: `recency` (newest start first, the default) or `volume` (largest search-volume bucket first). | recency |
| hours | No | Window in hours: 4, 24, 48 or 168. Default: 24. Google Trends offers no other window. | |
| limit | No | Trends per page, 1 to 100. Default: 25. | |
| active | No | Only trends still active (`true`) or only ended ones (`false`). Omit for both. | |
| cursor | No | Cursor from `page.nextCursor` of the previous response. It only works with the same filters. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| category | No | Trending category id: `0` (all, default), 1 to 11 or 13 to 20; for example `17` is Sports. This is the trending list's own set, not the categories endpoint's tree. | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess. | |
| conversation_id | No | Echo the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it. |