Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Google Trends topic suggestions

google_trends_suggestions_list
Read-onlyIdempotent

Lists topic suggestions Google Trends provides for a given text, helping you find related search topics to expand keyword ideas and content angles.

Instructions

List the topics Google Trends suggests for a text. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "google_trends_suggestions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Text to suggest topics for, 1 to 120 characters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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
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 the safety profile is covered. The description adds almost nothing beyond that — it does not mention that conversation_id must be echoed from a prior response, that parallel calls should be avoided before it is received, or anything about suggestion volume or rate limits.

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?

Three terse sentences with the core action front-loaded and no filler. 'Returns a list' earns its place slightly because there is no output schema, though 'Requires `query`' duplicates the schema and could be dropped.

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

Completeness4/5

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

For a simple read-only list endpoint whose parameters are fully documented in-schema and whose safety profile is fully annotated, the description is nearly sufficient. The one real gap is the conversation_id handshake protocol, which materially affects how an agent sequences calls and is absent from the description text.

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 all five parameters including the unusual context, llm_model and conversation_id fields are documented in-schema. The description's 'Requires `query`' merely restates a schema constraint and adds no new meaning, which is the baseline-3 case.

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?

Names a specific verb and resource: listing topic suggestions that Google Trends proposes for a given text. That is distinguishable from retrieval siblings like interest_over_time_get or trending_list, though it never explicitly contrasts itself with suggestion-adjacent tools such as google_news_suggest_list or google_trends_categories_list.

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 a prerequisite ('Requires `query`'), which is already enforced by the required-parameters list in the schema. There is no statement of when to choose this over the related-queries or categories tools, and no conditions or exclusions.

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