Get Google Trends related queries
google_trends_related_queries_getRetrieve top and rising related Google Trends queries for a search term or topic to identify related search demand and emerging interests by location and time range.
Instructions
Get the top and rising related queries on Google Trends. Requires query.
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": {
"query": "<query>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "google_trends_related_queries_get"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| geo | No | Place: a country code (`US`, `DE`), a subdivision (`US-CA`, `DE-BY`) or an empty string for worldwide. Lowercase input is accepted and normalised to uppercase. Default: `US`. | US |
| time | No | Time range: `now 1-H`, `now 4-H`, `now 1-d`, `now 7-d`, `today 1-m`, `today 3-m`, `today 12-m`, `today 5-y`, `all`, or a custom `YYYY-MM-DD YYYY-MM-DD` range (hourly `YYYY-MM-DDTHH` is accepted). | today 12-m |
| query | Yes | Required. One search term, or a topic as `id:` followed by a Knowledge Graph id (`id:/m/02vqfm`). A single term may contain a comma; send it as one parameter value. | |
| source | No | Property to search: `web` (default), `images`, `news`, `youtube` or `shopping`. | web |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| category | No | Category id from the categories endpoint. `0` (the default) means all categories. | |
| language | No | Interface language, as Google calls `hl` (`en-US`, `de`, `ja`, `ar`). It localises names, dates and type text; it does not translate the queries. | en-US |
| 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. |