Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Google Trends trending searches

google_trends_trending_list
Read-onlyIdempotent

Fetch trending Google searches by country or region, then filter by time window, category, activity status, and sort order.

Instructions

List the searches trending on Google Trends by place. Optional inputs: geo, hours, category, active, sort and 2 more. Returns a list (use cursor when paginated).

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_trending_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNoPlace: an ISO 3166-1 country code (`US`, `DE`) or a subdivision code (`US-CA`, `DE-BY`). Lowercase input is accepted and normalised to uppercase. Default: `US`.US
sortNoHow to order the list: `recency` (newest start first, the default) or `volume` (largest search-volume bucket first).recency
hoursNoWindow in hours: 4, 24, 48 or 168. Default: 24. Google Trends offers no other window.
limitNoTrends per page, 1 to 100. Default: 25.
activeNoOnly trends still active (`true`) or only ended ones (`false`). Omit for both.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
categoryNoTrending category id: `0` (all, default), 1 to 11 or 13 to 20; for example `17` is Sports. This is the trending list's own set, not the categories endpoint's tree.
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 readOnly=true, destructive=false, idempotent=true and openWorld=true, so the safety profile is fully covered elsewhere. The description adds that the result is a list and that pagination uses a cursor, but says nothing about rate limits, data freshness, or what the trend entries contain, leaving the behavioral picture thin for a 10-parameter tool.

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

Conciseness3/5

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

Two sentences, front-loaded and free of padding, which is good. But the middle clause enumerating parameter names is redundant against a 100%-covered schema, and "and 2 more" is an imprecise formulation that spends words without conveying information.

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?

For a tool with 10 parameters, no output schema and an open-world data source, the description should say more about what a returned trend entry looks like and how paging terminates. The cursor hint plus the read-only annotations cover the basics, but return-shape detail is missing.

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 (geo, hours, sort, category, cursor, active, etc.) is already fully documented, including enums, defaults and formats. The description merely echoes parameter names ("geo, hours, category, active, sort and 2 more") without adding meaning; the "and 2 more" also omits context and llm_model, which the schema covers anyway.

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?

The description gives a specific verb and resource ("List the searches trending on Google Trends") and adds the scoping dimension ("by place"). It does not, however, distinguish itself from the close sibling google_trends_trending_headlines_list, so an agent must infer the difference from the names alone.

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?

There is no guidance on when to pick this tool over the many sibling trend/headline/report tools, and no exclusions or prerequisites. The only usage instruction is the pagination note "use cursor when paginated", which is about mechanics, not tool selection.

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