Skip to main content
Glama

SEO Trends API

trends___get_growth

Read-onlyIdempotent

Point-to-point growth for a keyword on one or more sources. Each window is a preset string (12M, 3M, YTD, and the other listed periods). Values are on a 0-100 scale, plus absolute volume when available. Designed for growth questions; for charting or custom math, get_time_series provides the full series. App Downloads and App Rankings are keyword sources (Android bundle ID). They are not the App Store / Google Play live boards on get_top_trends. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

Input Schema

NameRequiredDescriptionDefault
sourceYesOne source, or comma-separated sources (e.g. 'Amazon, TikTok, YouTube'). Valid: 'Google Search', 'Google Images', 'Google News', 'Google Shopping', 'YouTube', 'Wikipedia', 'TikTok', 'Amazon', 'npm', 'Python', 'Steam', 'App Downloads', 'App Rankings'.
countryNoOptional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'UK' or 'United Kingdom' resolve too. Only for Google Search, Google Images, Google News, Google Shopping, YouTube, and TikTok. Google defaults to worldwide, TikTok to US; with a country the data is fetched live.
keywordYesWhat to look up. The string format is required by source. Standard sources (Google Search, Google Images, Google News, Google Shopping, YouTube, Wikipedia, TikTok, Amazon): any name or phrase, e.g. 'nike'. npm: Exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. Python: Exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. Steam: Game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. App Downloads and App Rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART. If the request includes App Downloads or App Rankings with other sources, keyword must still be the Android bundle ID.
languageNoOptional language edition code (en, de, ja, pt). Only for Wikipedia. Default en; other languages are fetched live.
resolutionNoOptional. 'weekly' (default, about 5 years) or 'daily' (last 90 days, fetched live). Only for Google Search, Google Images, Google News, Google Shopping, and YouTube.
percent_growthNoGrowth windows. Default if omitted: ['12M']. Each item must be a preset string: '7D', '1W', '14D', '2W', '30D', '1M', '2M', '3M', '6M', '9M', '12M', '1Y', '18M', '24M', '2Y', '36M', '3Y', '48M', '4Y', '60M', '5Y', 'MTD', 'QTD', 'YTD'. Every preset is a two-date comparison.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "Optional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'UK' or 'United Kingdom' resolve too. Only for Google Search, Google Images, Google News, Google Shopping, YouTube, and TikTok. Google defaults to worldwide, TikTok to US; with a country the data is fetched live.",
      +  "type": "string"
      +}
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Optional language edition code (en, de, ja, pt). Only for Wikipedia. Default en; other languages are fetched live.",
      +  "type": "string"
      +}
    • addedInput schema / properties / resolution
      Added value: +{
      +  "description": "Optional. 'weekly' (default, about 5 years) or 'daily' (last 90 days, fetched live). Only for Google Search, Google Images, Google News, Google Shopping, and YouTube.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"What to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, amazon): any name or phrase, e.g. 'nike'. npm: exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. python: exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. steam: game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. app downloads and app rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART. If the request includes app downloads or app rankings with other sources, keyword must still be the Android bundle ID."New value: +"What to look up. The string format is required by source. Standard sources (Google Search, Google Images, Google News, Google Shopping, YouTube, Wikipedia, TikTok, Amazon): any name or phrase, e.g. 'nike'. npm: Exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. Python: Exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. Steam: Game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. App Downloads and App Rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART. If the request includes App Downloads or App Rankings with other sources, keyword must still be the Android bundle ID."
    • changedInput schema / properties / source / description
      Previous value: -"One source, or comma-separated sources (e.g. 'amazon, tiktok, youtube'). Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'amazon', 'npm', 'python', 'steam', 'app downloads', 'app rankings'."New value: +"One source, or comma-separated sources (e.g. 'Amazon, TikTok, YouTube'). Valid: 'Google Search', 'Google Images', 'Google News', 'Google Shopping', 'YouTube', 'Wikipedia', 'TikTok', 'Amazon', 'npm', 'Python', 'Steam', 'App Downloads', 'App Rankings'."
  3. Changed2 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"What to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, reddit, amazon, news sentiment, news volume): any name or phrase, e.g. 'nike'. npm: exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. python: exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. steam: game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. app downloads and app rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART. If the request includes app downloads or app rankings with other sources, keyword must still be the Android bundle ID."New value: +"What to look up. The string format is required by source. Standard sources (google search, google images, google news, google shopping, youtube, wikipedia, tiktok, amazon): any name or phrase, e.g. 'nike'. npm: exact npmjs.com package name, case-sensitive. Right: 'react', '@babel/core'. Wrong: 'React', 'React.js'. python: exact PyPI project name. Right: 'pandas', 'requests'. Wrong: 'Pandas'. steam: game display name in plain English, not a Steam App ID. Right: 'Elden Ring', 'CS2'. First Steam store search result wins, so use an unambiguous name. app downloads and app rankings: Android bundle ID only (the id= value on Google Play). Right: 'com.openai.chatgpt', 'com.whatsapp'. Wrong: 'ChatGPT', 'WhatsApp', an iOS App Store ID, or a bundle ID that is not Android. Find it at play.google.com/store/apps/details?id=THIS_PART. If the request includes app downloads or app rankings with other sources, keyword must still be the Android bundle ID."
    • changedInput schema / properties / source / description
      Previous value: -"One source, or comma-separated sources (e.g. 'amazon, tiktok, youtube'). Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'reddit', 'amazon', 'news sentiment', 'news volume', 'npm', 'python', 'steam', 'app downloads', 'app rankings'."New value: +"One source, or comma-separated sources (e.g. 'amazon, tiktok, youtube'). Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'amazon', 'npm', 'python', 'steam', 'app downloads', 'app rankings'."
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds behavior beyond them: values are on a 0-100 scale with absolute volume when available, and a plan-limit message is returned on rate limit or quota exhaustion. It does not describe pagination or failure modes beyond the quota message, so not a 5.

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?

Front-loads the purpose and the sibling routing in the first two sentences, then handles clarifications. Slightly padded by restating the preset-window format already enumerated in the schema, but nothing is wasted overall.

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?

No output schema exists, so the description correctly supplies return semantics (0-100 scale, optional absolute volume) and quota-limit behavior. Given six parameters with rich schema coverage, this is nearly sufficient; a bit more on what a per-source/per-window result collection looks like would close the gap.

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 schema carries the parameter burden with detailed per-source keyword formats, country/language/resolution restrictions, and the full preset list. The description only restates that windows are preset strings like '12M' and that sources can be multiple, adding no semantics beyond the schema — baseline 3.

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 operation ('Point-to-point growth for a keyword on one or more sources') and immediately separates itself from get_time_series (full series) and get_top_trends (live app boards). An agent can distinguish this from every sibling 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?

Explicit routing: 'Designed for growth questions; for charting or custom math, get_time_series provides the full series.' It also preempts a likely confusion by clarifying that App Downloads/App Rankings are keyword sources here, not the live boards on get_top_trends.

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.