google-trends

Google Trends related queries

related_queries

Fetches top and rising related search queries for a keyword, including breakout terms that grew over 5000%, to help identify emerging search interests.

Instructions

Get the top and rising related search queries for a keyword. 'Breakout' means the query grew by more than 5000%.

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": {
      "keyword": "<keyword>"
    },
    "name": "related_queries"
  }
}

Input Schema

Name	Required	Description	Default
`geo`	No	Country or region code, e.g. US, GB, IN, PK, US-CA	US
`keyword`	Yes	The search term
`timeframe`	No	Google Trends time range	today 3-m

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully defines 'Breakout' as >5000% growth, which clarifies the return semantics, but says nothing about rate limits, quota behavior, or what happens for low-volume keywords with empty result sets.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core purpose and followed by the one piece of domain jargon an agent would otherwise misread. No wasted wording.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter read tool with no output schema, the description covers what is returned (top and rising queries) and defines the non-obvious 'Breakout' label. Only minor gaps remain, such as result shape or limits on the number of queries returned.

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%, with geo format, timeframe enum, and keyword all documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource: 'Get the top and rising related search queries for a keyword.' This clearly separates it from interest_over_time (a series over time) and trending_now (currently trending searches), though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is implied by 'for a keyword' and the top/rising framing, but there is no explicit statement of when to prefer this over interest_over_time or trending_now, and no prerequisites or exclusions are given.

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

Deploy Server