Retrieve the location codes supported by Google Trends so you can filter or target trend data by region, including WORLDWIDE.
Google Trends locations. Returns the list of location codes that Google Trends supports, such as US, HK and GB, in locations. The Explore endpoints also accept WORLDWIDE, which appears in the list. It takes no parameters.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden and does so well: it discloses the return field name (`locations`), the value format, the special `WORLDWIDE` entry, and that the tool takes no inputs. It stops short of any freshness/static-list or rate-limit context, but for a parameterless enumeration that is minor.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short, front-loaded sentences, each earning its place: purpose, output/format, and the WORLDWIDE caveat. No filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and a trivial input surface, the description supplies exactly what the agent needs: what is returned, under which key, and the notable edge value. Nothing material is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so per the rubric the baseline is 4. The description reinforces this by explicitly stating 'It takes no parameters,' leaving no ambiguity for the agent.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Returns the list of') and resource ('location codes that Google Trends supports'), with concrete examples (`US`, `HK`, `GB`). An agent can immediately distinguish this enumeration tool from the explore/trending siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It notes that Explore endpoints accept `WORLDWIDE`, which hints at how the output feeds other calls, and states 'It takes no parameters.' However it never explicitly says when to use this versus the nearby `google_trends_enums` or `google_trends_categories` tools, so usage is implied rather than prescribed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.