Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Google Trends interest over time

google_trends_interest_over_time_get
Read-onlyIdempotent

Track and compare Google Trends search interest over time for one to five terms across regions, time ranges, and sources to identify demand shifts.

Instructions

Get Google Trends search interest over time 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_over_time_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
timeNoOne or two ranges for one term; two must differ. Named `now 1-H`/`4-H`/`1-d`/`7-d`, `today 1-m`/`3-m`/`12-m`/`5-y`, `all`; custom `YYYY-MM-DD YYYY-MM-DD`; named pairs must match in length. Default: `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.
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds nothing beyond that: it does not explain that results are a relative 0-100 index, that values are normalized per request, or how sampled/partial data behaves — context an agent would need to interpret output.

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, front-loaded with the primary action, with zero filler. It is efficient, though the second sentence largely repeats a schema requirement.

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 nine parameters (including harness parameters like context, llm_model and conversation_id) and no output schema, the description is thin — it says nothing about the shape or semantics of the returned time series. The rich input schema compensates for parameter documentation but not for return-value understanding.

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 the geo, time, source, category, language and query parameters are already fully documented with formats and defaults. The description merely restates the query constraint, adding no meaning beyond the schema; 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 over time") and adds a scope constraint (one to five terms). Combined with the name, it is clearly distinguishable from siblings like google_trends_interest_by_region_get, though it never explicitly contrasts itself with them.

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?

No guidance on when to use this versus interest_by_region_get, related_queries_get, or report_get, and no exclusions or prerequisites beyond "Requires query". The agent must infer routing from the tool name alone.

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