Skip to main content
Glama

google_trends

        Returns the Google Trends interest-over-time series for one phrase: one row per point in time
        with the interest value (0-100). Use it to see whether demand for a product or a topic grows,
        falls or is seasonal, in one country or worldwide. The rows come back in the answer at once;
        nothing is saved to the account.

        Price: 10 credits per call. Send quote_only=true to get the exact price in money
        and the wallet balance without spending anything.

        Args:
          - query (required): the phrase.
          - geo (optional): ISO country code such as US or EE. Omit for worldwide. A name ("Estonia")
            is refused - a wrong region would silently answer the worldwide series.
          - date (optional): now 1-H, now 4-H, now 1-d, now 7-d, today 1-m, today 3-m, today 12-m
            (default), today 5-y or all.
          - idempotency_key (optional): send the same value when you retry; answered and charged once.
          - quote_only (optional): true = price only.

        Returns:
          status DONE with `rows` (text values are wrapped as {type: "scraped", content, origin,
          truncated}; numbers are plain), `rowCount`, `costMicros`, `quote`, `walletBalanceMicros`,
          `freeRequestsLeft`, `truncated`, `replayed`. With quote_only: status QUOTE and no rows.

        Examples:
          - Use when: "is interest in e-bikes growing in Germany" -> query "e-bike", geo "DE", date
            "today 5-y".
          - Use when: checking seasonality before a campaign -> date "today 12-m".
          - Don't use when: you want what is trending right now in a country -> not in this list yet.
          - Don't use when: you want search results for the phrase -> use google_search.

        Error Handling:
          - 400 INVALID_QUERY / INVALID_GEO / INVALID_DATE: the named input is wrong; nothing was
            charged.
          - 402: the wallet has no balance and no free requests.
          - 403: the API key is read-only.
          - 409 MCP_REQUEST_IN_PROGRESS / IDEMPOTENCY_KEY_REUSED: see idempotency_key.
          - 429 MCP_QUICK_BUSY: too many calls at the same moment; wait Retry-After.
          - 401 Unauthorized.

[runtime hint] This tool returns JSON-as-text — its response shape is dynamic (per-scraper itemsConfig, file binary, etc.) so the MCP outputSchema is omitted. Do not rely on the presence of any specific field in the response; treat the result as a string-or-object blob and parse defensively.

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": {
      "body": "<body>"
    },
    "name": "google_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesGoogle Trends interest over time for one phrase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Goes well past the annotations: discloses the 10-credit cost, the free quote_only price-check path, that results come back synchronously with nothing persisted to the account, idempotency replay behavior, and a full error-code table with charge implications. The only shortfall is that readOnlyHint=false is never reconciled with the 'nothing is saved' claim — an agent must infer the flag reflects credit spend rather than data mutation.

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?

Well front-loaded and sectioned with Args/Returns/Examples/Error Handling, and the pricing line is placed where it matters. It loses a point for restating the date enum and parameter list verbatim from the schema, which is redundant given full structured coverage.

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

Completeness5/5

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

For a paid, single-shot scraping tool with no output schema and a dynamically shaped response, the description covers the return fields, quote_only variant, truncation and replay flags, error codes, and cost. An agent has everything needed to call it correctly and interpret the result.

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 coverage is already 100%, so the baseline is 3, but the description adds genuine meaning beyond it: geo rejects country names like 'Estonia' because a wrong region would silently return worldwide data, and idempotency_key explains the charged-once retry contract. The date enum and query text are largely restated from the schema, which caps the score below 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — returns the Google Trends interest-over-time series for one phrase, one row per time point with a 0-100 interest value — and explicitly excludes the sibling google_search for search-result needs. An agent can distinguish it from every listed alternative without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides concrete when-to-use scenarios (is interest in e-bikes growing in Germany, checking seasonality before a campaign) plus explicit when-not-to-use cases, including a named redirect to google_search and an honest note that trending-now is not yet supported. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.