Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Google Trends places

google_trends_geos_list
Read-onlyIdempotent

List the places Google Trends explore requests accept, filtered by language, country, or level to target the right geographic area.

Instructions

List the places Google Trends explore requests accept. Optional inputs: language, country and level. Returns a list.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "google_trends_geos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoOnly places at this level: `country`, `subdivision` (states, provinces, regions) or `metro` (US Nielsen DMAs).
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoOnly the places of this country, e.g. `US`.
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

A3.5/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 'Returns a list', leaving out whether the result set is large, static reference data, or how the list relates to subsequent explore calls — some added context but thin.

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 resource being listed, no filler. 'Returns a list' is close to redundant but does supply the only return-value signal available since there is no output schema.

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 no output schema, the description should indicate the shape of the returned places (e.g. name plus geo identifier) so an agent knows what to feed into explore calls; it only says 'a list'. Parameter documentation is fully handled by the schema, so the gap is confined to the return-value contract.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already defines `language`, `country` (ISO-2 pattern) and the `level` enum. The description correctly identifies exactly which inputs are optional and worth filtering on, which is a small but real addition over the schema. Baseline 3 is exceeded only slightly since the schema carries nearly all the meaning.

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?

Specific verb plus resource: it lists the places accepted by Google Trends explore requests, which is a concrete enumeration/lookup purpose. It is distinguishable from the sibling list tools (categories, suggestions, trending), though the description never names them 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?

The mention of `country` and `level` filters implies you call this to narrow down valid place identifiers, likely before issuing an explore/interest request, but the description never states that workflow or any when-not condition. Usage is inferable 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