Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Google Trends report

google_trends_report_get
Read-onlyIdempotent

Fetch Google Trends interest over time, regional breakdowns, and related queries in one request by supplying a search term. Use it to compare demand patterns and spot emerging topics.

Instructions

Get Google Trends interest over time, by region and related queries in one request. 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_report_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.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 that results span three facets in a single request, which is useful context, but says nothing about result shape, limits, or the conversation_id sequencing rule stated only in the schema.

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 tight sentences with the capability front-loaded and zero filler. Brevity is appropriate, though the second sentence is arguably redundant with the schema's required field.

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 a 9-parameter, 3-required tool with no output schema, the description is thin: it does not sketch the report's structure, mention geo/time defaults, or note the sequential conversation_id requirement. It relies almost entirely on the schema to make the tool callable correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter statement is 'Requires `query`', which merely repeats the schema's required list. With 9 parameters including context, llm_model, and conversation_id conventions, the description adds nothing the schema does not already say.

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 and names the three data sections returned (interest over time, by region, related queries), which implicitly distinguishes it from the granular sibling tools like google_trends_interest_over_time_get and google_trends_related_queries_get. It never names those siblings explicitly, so the differentiation requires inference.

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?

The phrase 'in one request' hints that this is the aggregate alternative to the three single-facet siblings, but the description never states when to prefer it over them or any exclusions. Usage is implied rather than stated.

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