Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Google Trends related queries

google_trends_related_queries_get
Read-onlyIdempotent

Retrieve 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

NameRequiredDescriptionDefault
geoNoPlace: 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
timeNoTime 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
queryYesRequired. 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.
sourceNoProperty to search: `web` (default), `images`, `news`, `youtube` or `shopping`.web
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
categoryNoCategory id from the categories endpoint. `0` (the default) means all categories.
languageNoInterface 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_modelYesThe 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_idNoEcho 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the useful fact that results are split into 'top' and 'rising' sets, which is genuine behavioral information, but it says nothing about result shape, quotas, or rate limiting on a live third-party source.

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

Conciseness4/5

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

Two short sentences with the capability first and the requirement second; nothing is wasted. It is efficiently written, though efficiency here shades into under-specification rather than exemplary terseness.

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

Completeness3/5

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

With 9 parameters, no output schema, and rich annotations, the definition is minimally viable: parameter meaning is fully carried by the schema and safety by annotations. However, with no output schema the description should have sketched the top/rising return structure and when this tool beats its interest_* siblings, and it does neither.

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%, so every parameter including geo, time, source, language and category is already documented in detail. The description only echoes the `query` requirement and adds no meaning beyond the schema, which matches the baseline 3.

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 queries on Google Trends'), and the phrase 'related queries' plus 'top and rising' distinguishes it from interest_over_time and interest_by_region siblings. It stops short of naming an alternative, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

The only guidance is 'Requires `query`', which restates the schema's required field. There is no statement of when to reach for this tool versus google_trends_interest_over_time_get or google_trends_report_get, and no prerequisites or exclusions.

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

Deploy Server

Other Tools