Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Google Trends interest by region

google_trends_interest_by_region_get
Read-onlyIdempotent

Compare Google Trends search interest by region for one to five terms to see where each topic is popular.

Instructions

Get Google Trends search interest by place for one to five terms. 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_interest_by_region_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 to five search terms, comma-separated or repeated when a term contains a comma. A topic is `id:` plus a Knowledge Graph id (`id:/m/02vqfm`), as the suggestions endpoint returns it.
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.
resolutionNoRegion resolution: `region` for subdivisions, `dma` for US metro areas, or `city`. The default is the one Google Trends picks for the geo. A place without a city-level breakdown is refused as input.
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.
includeLowVolumeNoInclude places with too little search volume to appear by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/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 only the term-count constraint and the query requirement, saying nothing about rate limits, result shape, or the conversation_id sequencing the schema hints at.

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 resource and the key constraint front-loaded; nothing is wasted. It is efficient but so terse that it omits useful context rather than padding.

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

Completeness2/5

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

For an 11-parameter tool with no output schema, the description is far too thin: it does not explain the geo/resolution interaction, the conversation_id handshake, or what the response contains. An agent must rely entirely on the schema to call this correctly.

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 is already documented in the schema, including geo, time, resolution and source. The description's "one to five terms" merely restates the schema's minItems/maxItems, so 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 Google Trends search interest by place") and scopes it to one to five terms, which distinguishes it from the over-time sibling. It stops short of naming the alternative explicitly, so it is clear but not maximally differentiating.

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 the prerequisite "Requires `query`." There is no statement of when to choose this tool over google_trends_interest_over_time_get or google_trends_report_get, and no exclusions or conditions 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

Other Tools