Skip to main content
Glama

Amazon Trends MCP

by ai.trendsmcp
OverviewDiscussionsAdmin

Server Details

Amazon product search demand over time, with growth for any keyword. Free key at trendsmcp.ai

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
14.1% over 75 days
Last Tested
Transport
Streamable HTTP · MCP 2025-03-26
URL
Repository
trendsmcp-ai/amazon-trends-mcp
GitHub Stars
0
Server Listing
amazon-trends-mcp

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation4/5

Each tool has a distinct job, and the descriptions actively cross-reference each other (get_growth for growth, get_time_series for charting, get_context for qualitative conversation), which resolves most confusion. The residual risk is that get_context, get_growth, and get_time_series all take a keyword and return related numbers, so an agent asking a vague 'what's happening with X' question could still pick the wrong one.

Naming Consistency5/5

All six tools share the same namespace prefix and a uniform get_<noun> pattern (get_context, get_growth, get_time_series, get_top_posts, get_top_trends, get_usage). No mixed casing or verb styles.

Tool Count5/5

Six tools is well-scoped for a trends/data-lookup server: qualitative context, growth, raw series, live posts, live boards, and account usage. No filler tools and no obvious redundancy.

Completeness3/5

The analytical surface (context, growth, series, boards, posts, quota) is coherent, but there is no discovery tool: nothing lists valid sources, feeds, categories, or periods, and no keyword search/suggestion, so agents must guess valid inputs or rely on external docs. A multi-keyword comparison is also absent, which forces chained calls for common questions.

Available Tools

6 tools
trends___get_contextA
Read-onlyIdempotent
Inspect

What people are posting, reading and betting about a keyword right now. Returns recent posts, videos, news stories, discussions and prediction markets per source, with engagement (views, likes, score) and top comments. Use it to explain why something is trending or what the conversation says; get_time_series and get_growth measure how much. Costs 1 request per source. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

NameRequiredDescriptionDefault
daysNoLook back this many days, 1 to 30. Default 7.
limitNoItems per source, 1 to 20. Default 10.
sourceYesOne source, or up to 5 comma-separated. Valid: 'News', 'YouTube', 'TikTok', 'Instagram', 'X', 'Reddit', 'Bluesky', 'Hacker News', 'Polymarket', 'GitHub'.
keywordYesAny name or phrase, e.g. 'nintendo switch 2'.
commentsNoTop comments for the first N items of each source, 0 to 5. Default 2. Only for 'YouTube', 'TikTok', 'Instagram', 'X', 'Reddit', 'Bluesky', and 'Hacker News'.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely non-structured behavior: cost of 1 request per source, and that a plan-limit message is returned when rate limited or the monthly quota is exhausted — useful operational context an agent cannot get elsewhere.

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

Conciseness5/5

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

Front-loaded with what it returns, then the distinguishing use case, then cost and error behavior. Every sentence carries distinct information; no restatement of the tool name or filler.

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?

No output schema exists, so the description must describe return values — and it does, enumerating item types, engagement metrics and top comments. Combined with cost and quota-message disclosure, an agent has everything needed to call this correctly and interpret limits.

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 baseline is 3. The description still adds meaning by tying results to sources ('per source') and clarifying that comments and engagement are per-item, which explains how the source, limit and comments parameters interact.

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-plus-resource: retrieves what people are posting, reading and betting about a keyword right now, returning posts, videos, news, discussions and prediction markets. It also explicitly distinguishes itself from the measurement siblings ('get_time_series and get_growth measure how much'), so an agent can pick correctly without opening another 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?

Gives an explicit use case ('use it to explain why something is trending or what the conversation says') and names the alternative tools with the condition that selects them (measurement vs. explanation). Nothing about when to reach for it 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.

trends___get_growthA
Read-onlyIdempotent
Inspect

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.

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', 'Pinterest', '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, TikTok, and Pinterest. 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, Pinterest): 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.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds value beyond them: output values are on a 0-100 scale with absolute volume when available, and rate-limited or quota-exhausted requests return a plan-limit message rather than data. It stops short of describing response structure per window, but the scale and failure mode are disclosed.

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?

Purpose is front-loaded in the first sentence, and alternatives follow immediately. The final two sentences on app-source caveats and plan limits are somewhat dense and partially duplicate schema text, but each carries actionable information.

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?

With no output schema, the description carries the burden of explaining returns, and it does so at a high level (0-100 scale plus absolute volume). Rate-limit behavior is covered. What's missing is the shape of the per-window result, but the essentials for calling correctly are present.

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 coverage is 100%, so per-parameter meaning is already fully documented in the schema. The description mostly restates it ('each window is a preset string') and adds no new syntax or constraints for country, language, or resolution. Baseline 3 applies when the schema does the heavy lifting.

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 ('Point-to-point growth for a keyword on one or more sources') with explicit scope. It distinguishes itself from siblings by naming get_time_series for full series and get_top_trends for live app boards, so an agent can choose without opening another 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?

'Designed for growth questions; for charting or custom math, get_time_series provides the full series' gives an explicit use case and a named alternative with the condition that selects it. The clarification that App Downloads/App Rankings are keyword sources rather than the live boards on get_top_trends prevents a realistic misselection.

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

trends___get_time_seriesA
Read-onlyIdempotent
Inspect

Full historical series for one keyword and one source (0-100 values, plus volume when available). Suited for charting or custom math. Live 'what's trending now' boards are on get_top_trends. get_growth answers most growth questions with less data. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

NameRequiredDescriptionDefault
sourceYesExactly one source per request. Valid: 'Google Search', 'Google Images', 'Google News', 'Google Shopping', 'YouTube', 'Wikipedia', 'TikTok', 'Amazon', 'Pinterest', '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, TikTok, and Pinterest. 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, Pinterest): any name or phrase, e.g. 'tesla'. 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.
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.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real value beyond them: the 0-100 normalized value range, optional volume, and the fact that a plan-limit message is returned on rate limiting or monthly quota exhaustion. It stops short of describing series length, gaps, or response envelope details.

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?

Four compact sentences, front-loaded with the core capability and followed by alternatives and the quota caveat. Slightly clipped phrasing ('get_growth answers most growth questions with less data') reads as telegraphic but wastes no space.

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?

With 5 parameters, 100% schema coverage, no output schema, and full annotations, the description covers purpose, routing, output scale, and quota failure mode. Return structure is only sketched (values plus volume) but the missing detail is minor given the schema's thoroughness.

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%, and the source parameter already documents per-source keyword formats, country, language, and resolution constraints in detail. The description only reinforces the single-source-per-request rule, adding little beyond what the schema carries. Baseline 3 is correct when the schema does the heavy lifting.

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 ('Full historical series for one keyword and one source') and immediately qualifies the output shape (0-100 values, plus volume when available). It explicitly names two siblings it is not (get_top_trends, get_growth), so an agent can route without opening any 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?

Gives positive usage ('Suited for charting or custom math') and explicit alternatives with conditions: get_top_trends for live trending boards, get_growth for most growth questions with less data. This is the when/when-not/alternative pattern done properly.

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

trends___get_top_postsA
Read-onlyIdempotent
Inspect

Live top posts for one hashtag on one social source. Fetched live on every call; nothing is stored. For when the user already has a hashtag and wants the posts winning on it. get_top_trends ranks the hashtags themselves. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

NameRequiredDescriptionDefault
limitNoMax posts to return. Default 20, min 1, max 20.
sourceYesExactly one source per request. Valid: 'TikTok', 'Instagram'.
keywordYesThe hashtag, with or without '#'. Spaces are removed. Example: 'bookstagram' or '#fitness'.

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing that data is fetched live every call with no storage, and that a plan-limit message is returned on rate limiting or monthly quota exhaustion — operationally important for an agent's retry logic. It stops short of describing the actual post payload or ordering, so it is very good rather than complete.

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

Conciseness5/5

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

Four short sentences, each carrying distinct information: what it returns, freshness semantics, when to pick it, the sibling alternative, and the failure mode. The core scope is stated first with no preamble.

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?

With no output schema, the description still conveys the shape at a high level ('top posts' per hashtag/source) and covers the quota failure mode. Slight gap: it does not describe ordering or how results are ranked, nor whether an empty result is possible for an unknown hashtag.

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 coverage is 100% and the schema documents all three parameters including the valid source values and the limit default/min/max, so the description correctly defers. It adds nothing extra about parameter behavior, which is the expected baseline here.

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 ('Live top posts') bounded to exactly one hashtag and one source, and explicitly contrasts with the sibling that ranks hashtags instead. An agent can distinguish it from get_top_trends without opening either 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?

'For when the user already has a hashtag and wants the posts winning on it' gives the selecting condition, and 'get_top_trends ranks the hashtags themselves' names the alternative and its own condition. Both sides of the routing decision are explicit.

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

trends___get_top_trendsA
Read-onlyIdempotent
Inspect

Live top-trending board for exactly one feed type. No keyword. For 'Amazon Best Sellers by Category', 'Google Trends by Category', 'Pinterest Trending by Category', 'Top Websites', 'Substack by Category', and 'TikTok Trending Hashtags by Category', category selects the board. Default sort is current rank. Use sort='rank_change' for climbers vs a prior snapshot (window 1d, 3d, 7d, 14d, or 30d). If the requested board is not in the database yet (for example a country that is not collected on the schedule), the board is fetched live. App Store Top Free, App Store Top Paid, and Google Play are live store boards, not keyword lookups. App history is available via get_growth or get_time_series with source App Downloads or App Rankings and an Android bundle ID. Live boards are only available here, not via get_time_series. Returns a plan-limit message when the request is rate limited or the monthly quota is used up.

NameRequiredDescriptionDefault
sortNoHow to rank the board. 'rank' (default): current leaders. 'rank_change': biggest climbers vs a prior snapshot. Mover rows include rank, keyword, prev_rank, and rank_change.
typeYesExactly one live feed. Valid: 'Amazon Best Sellers Top Rated', 'Amazon Best Sellers by Category', 'App Store Top Free', 'App Store Top Paid', 'GitHub', 'Google News Top News', 'Google Play', 'Google Trends', 'Google Trends by Category', 'IMDb MOVIEmeter', 'Open Library Trending Books', 'Pinterest Trending', 'Pinterest Trending by Category', 'Polymarket Top Markets', 'Reddit Hot Posts', 'Reddit World News', 'Top Websites', 'Spotify Top Podcasts', 'Steam Most Played', 'Substack', 'Substack by Category', 'TikTok Trending Hashtags', 'TikTok Trending Hashtags by Category', 'TikTok Trending Searches', 'Wikipedia Trending', 'X (Twitter) Trending', 'YouTube Trending'.
limitNoMax rows to return. Default 25, min 1, max 200.
offsetNoRows to skip for pagination. Default 0.
windowNoLookback used only when sort is 'rank_change'. One of '1d', '3d', '7d', '14d', '30d'. Default '30d'. Short windows only work on daily feeds; weekly and monthly feeds return a note pointing to a longer window.
countryNoOptional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'USA' or 'United States' resolve to US. Omit for the default US board. Only for Google Trends, Google Trends by Category, Pinterest Trending, Pinterest Trending by Category, TikTok Trending Hashtags, TikTok Trending Hashtags by Category, X (Twitter) Trending, and YouTube Trending.
categoryNoPass this whenever type is 'Amazon Best Sellers by Category', 'Google Trends by Category', 'Pinterest Trending by Category', 'Top Websites', 'Substack by Category', or 'TikTok Trending Hashtags by Category'. Use the official name. Without it those feeds mix every board. Only omit on a first pull to learn the official names.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish readOnly/idempotent/openWorld, yet the description adds real behavior: a live fetch occurs when the requested board isn't in the database, short windows on weekly/monthly feeds return a note pointing to a longer window, and rate-limited or quota-exhausted requests return a plan-limit message. These are operational traits an agent cannot infer from annotations or schema.

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-loaded with the core purpose and the key constraint ('No keyword'), then layered with exceptions. Some redundancy with the schema – the six category-dependent board names are repeated verbatim from the type description – but every sentence carries operational information.

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 7-parameter, no-output-schema tool with sibling alternatives, the description covers usage, fallback behavior, quotas, and partial return semantics (plan-limit messages, mover row fields). It stops short of 5 because the general row shape for non-mover results is left entirely unstated with no output schema to fill the gap.

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 100%, so the baseline is 3; the description earns a bump by explaining cross-parameter relationships the schema lists only per-property – that window is meaningful only under sort='rank_change' and that category 'selects the board' rather than filtering results. It largely restates the parameter list, so it stops short of 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?

Opens with a specific verb and resource ('Live top-trending board for exactly one feed type') and enumerates the board families it covers. It explicitly contrasts itself with siblings by stating 'Live boards are only available here, not via get_time_series,' so an agent can separate it from get_time_series and get_growth 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?

Gives concrete when-to-use rules: sort='rank_change' for climbers with a named window set, category required for six specific boards, and category omitted only on a first pull to learn official names. It also names the correct alternative for App Store history (get_growth or get_time_series with source App Downloads/App Rankings).

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

trends___get_usageA
Read-onlyIdempotent
Inspect

Shows your plan, requests used this month, requests left, and when it resets. Free: does not use a request. Call it when the user asks about their limit or after a limit error.

NameRequiredDescriptionDefault

No parameters

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely useful behavioral context not in the annotations: 'Free: does not use a request,' which matters for quota-awareness. It stops short of describing return format/pagination but no output schema exists.

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

Conciseness5/5

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

Two sentences, zero waste, with the return contents front-loaded ahead of the invocation guidance. Nothing extraneous.

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?

With zero params and no output schema, the description fully covers what the tool does and what it returns (plan, used, left, reset time) plus the cost note. An agent has everything needed to call it correctly.

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?

The tool takes zero parameters, so the baseline is 4. The schema is empty and there is nothing for the description to compensate for; no confusion is possible.

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?

Names a specific verb ('Shows') and enumerates the exact resource fields returned: plan, requests used, remaining, and reset time. An agent can clearly distinguish this diagnostic tool from the analytics siblings (get_growth, get_time_series, get_top_posts, get_top_trends).

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

Usage Guidelines4/5

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

Gives explicit trigger conditions: 'when the user asks about their limit' and 'after a limit error.' Clear invocation context. It doesn't name when-not-to-use or an alternative, but the siblings are unrelated analytics tools so an exclusion is less necessary.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updates
    • Changedtrends___get_growth3 fields changed
      • changedInput schema / properties / country / description
        Previous value: -"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."New value: +"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, TikTok, and Pinterest. Google defaults to worldwide, TikTok to US; with a country the data is fetched live."
      • 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, Pinterest): 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', 'Pinterest', 'npm', 'Python', 'Steam', 'App Downloads', 'App Rankings'."
    • Changedtrends___get_time_series3 fields changed
      • changedInput schema / properties / country / description
        Previous value: -"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."New value: +"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, TikTok, and Pinterest. Google defaults to worldwide, TikTok to US; with a country the data is fetched live."
      • 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. 'tesla'. 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."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, Pinterest): any name or phrase, e.g. 'tesla'. 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."
      • changedInput schema / properties / source / description
        Previous value: -"Exactly one source per request. Valid: 'Google Search', 'Google Images', 'Google News', 'Google Shopping', 'YouTube', 'Wikipedia', 'TikTok', 'Amazon', 'npm', 'Python', 'Steam', 'App Downloads', 'App Rankings'."New value: +"Exactly one source per request. Valid: 'Google Search', 'Google Images', 'Google News', 'Google Shopping', 'YouTube', 'Wikipedia', 'TikTok', 'Amazon', 'Pinterest', 'npm', 'Python', 'Steam', 'App Downloads', 'App Rankings'."
    • Changedtrends___get_top_trends3 fields changed
      • changedInput schema / properties / category / description
        Previous value: -"Pass this whenever type is 'Amazon Best Sellers by Category', 'Google Trends by Category', 'Top Websites', 'Substack by Category', or 'TikTok Trending Hashtags by Category'. Use the official name. Without it those feeds mix every board. Only omit on a first pull to learn the official names."New value: +"Pass this whenever type is 'Amazon Best Sellers by Category', 'Google Trends by Category', 'Pinterest Trending by Category', 'Top Websites', 'Substack by Category', or 'TikTok Trending Hashtags by Category'. Use the official name. Without it those feeds mix every board. Only omit on a first pull to learn the official names."
      • changedInput schema / properties / country / description
        Previous value: -"Optional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'USA' or 'United States' resolve to US. Omit for the default US board. Only for Google Trends, Google Trends by Category, TikTok Trending Hashtags, TikTok Trending Hashtags by Category, X (Twitter) Trending, and YouTube Trending."New value: +"Optional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'USA' or 'United States' resolve to US. Omit for the default US board. Only for Google Trends, Google Trends by Category, Pinterest Trending, Pinterest Trending by Category, TikTok Trending Hashtags, TikTok Trending Hashtags by Category, X (Twitter) Trending, and YouTube Trending."
      • changedInput schema / properties / type / description
        Previous value: -"Exactly one live feed. Valid: 'Amazon Best Sellers Top Rated', 'Amazon Best Sellers by Category', 'App Store Top Free', 'App Store Top Paid', 'GitHub', 'Google News Top News', 'Google Play', 'Google Trends', 'Google Trends by Category', 'IMDb MOVIEmeter', 'Open Library Trending Books', 'Polymarket Top Markets', 'Reddit Hot Posts', 'Reddit World News', 'Top Websites', 'Spotify Top Podcasts', 'Steam Most Played', 'Substack', 'Substack by Category', 'TikTok Trending Hashtags', 'TikTok Trending Hashtags by Category', 'TikTok Trending Searches', 'Wikipedia Trending', 'X (Twitter) Trending', 'YouTube Trending'."New value: +"Exactly one live feed. Valid: 'Amazon Best Sellers Top Rated', 'Amazon Best Sellers by Category', 'App Store Top Free', 'App Store Top Paid', 'GitHub', 'Google News Top News', 'Google Play', 'Google Trends', 'Google Trends by Category', 'IMDb MOVIEmeter', 'Open Library Trending Books', 'Pinterest Trending', 'Pinterest Trending by Category', 'Polymarket Top Markets', 'Reddit Hot Posts', 'Reddit World News', 'Top Websites', 'Spotify Top Podcasts', 'Steam Most Played', 'Substack', 'Substack by Category', 'TikTok Trending Hashtags', 'TikTok Trending Hashtags by Category', 'TikTok Trending Searches', 'Wikipedia Trending', 'X (Twitter) Trending', 'YouTube Trending'."
  2. 1 tool update
    • Changedtrends___get_top_trends1 field changed
      • changedInput schema / properties / type / description
        Previous value: -"Exactly one live feed. Valid: 'Amazon Best Sellers Top Rated', 'Amazon Best Sellers by Category', 'App Store Top Free', 'App Store Top Paid', 'GitHub', 'Google News Top News', 'Google Play', 'Google Trends', 'Google Trends by Category', 'IMDb MOVIEmeter', 'Open Library Trending Books', 'Reddit Hot Posts', 'Reddit World News', 'Top Websites', 'Spotify Top Podcasts', 'Steam Most Played', 'Substack', 'Substack by Category', 'TikTok Trending Hashtags', 'TikTok Trending Hashtags by Category', 'TikTok Trending Searches', 'Wikipedia Trending', 'X (Twitter) Trending', 'YouTube Trending'."New value: +"Exactly one live feed. Valid: 'Amazon Best Sellers Top Rated', 'Amazon Best Sellers by Category', 'App Store Top Free', 'App Store Top Paid', 'GitHub', 'Google News Top News', 'Google Play', 'Google Trends', 'Google Trends by Category', 'IMDb MOVIEmeter', 'Open Library Trending Books', 'Polymarket Top Markets', 'Reddit Hot Posts', 'Reddit World News', 'Top Websites', 'Spotify Top Podcasts', 'Steam Most Played', 'Substack', 'Substack by Category', 'TikTok Trending Hashtags', 'TikTok Trending Hashtags by Category', 'TikTok Trending Searches', 'Wikipedia Trending', 'X (Twitter) Trending', 'YouTube Trending'."
  3. 1 tool update
    • Addedtrends___get_context
  4. 2 tool updates
    • Changedtrends___get_growth3 fields changed
      • changedInput schema / properties / country / description
        Previous value: -"Optional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'UK' or 'United Kingdom' resolve too. Omit for worldwide. Only for Google Search, Google Images, Google News, Google Shopping, and YouTube; with a country the data is fetched live."New value: +"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."
      • 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"
+}
    • Changedtrends___get_time_series3 fields changed
      • changedInput schema / properties / country / description
        Previous value: -"Optional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'UK' or 'United Kingdom' resolve too. Omit for worldwide. Only for Google Search, Google Images, Google News, Google Shopping, and YouTube; with a country the data is fetched live."New value: +"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."
      • 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"
+}
  5. 3 tool updates
    • Changedtrends___get_growth3 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. Omit for worldwide. Only for Google Search, Google Images, Google News, Google Shopping, and YouTube; with a country the data is fetched live.",
+  "type": "string"
+}
      • 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'."
    • Changedtrends___get_time_series3 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. Omit for worldwide. Only for Google Search, Google Images, Google News, Google Shopping, and YouTube; with a country the data is fetched live.",
+  "type": "string"
+}
      • 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. 'tesla'. 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."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. 'tesla'. 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."
      • changedInput schema / properties / source / description
        Previous value: -"Exactly one source per request. Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'amazon', 'npm', 'python', 'steam', 'app downloads', 'app rankings'."New value: +"Exactly one source per request. Valid: 'Google Search', 'Google Images', 'Google News', 'Google Shopping', 'YouTube', 'Wikipedia', 'TikTok', 'Amazon', 'npm', 'Python', 'Steam', 'App Downloads', 'App Rankings'."
    • Changedtrends___get_top_posts1 field changed
      • changedInput schema / properties / source / description
        Previous value: -"Exactly one source per request. Valid: 'tiktok', 'instagram'."New value: +"Exactly one source per request. Valid: 'TikTok', 'Instagram'."
  6. 3 tool updates
    • Changedtrends___get_growth2 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'."
    • Changedtrends___get_time_series2 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. 'tesla'. 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."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. 'tesla'. 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."
      • changedInput schema / properties / source / description
        Previous value: -"Exactly one source per request. 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: +"Exactly one source per request. Valid: 'google search', 'google images', 'google news', 'google shopping', 'youtube', 'wikipedia', 'tiktok', 'amazon', 'npm', 'python', 'steam', 'app downloads', 'app rankings'."
    • Changedtrends___get_top_trends1 field changed
      • changedInput schema / properties / country / description
        Previous value: -"Optional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'USA' or 'United States' resolve to US. Omit for the default US board. Only for Google Trends, Google Trends by Category, YouTube Trending, TikTok Trending Hashtags, TikTok Trending Hashtags by Category, and X (Twitter) Trending."New value: +"Optional ISO 3166-1 alpha-2 code (US, GB, JP). Aliases like 'USA' or 'United States' resolve to US. Omit for the default US board. Only for Google Trends, Google Trends by Category, TikTok Trending Hashtags, TikTok Trending Hashtags by Category, X (Twitter) Trending, and YouTube Trending."
  7. 1 tool update
    • Addedtrends___get_usage
  8. 4 tool updates
    • First observedtrends___get_growth
    • First observedtrends___get_time_series
    • First observedtrends___get_top_posts
    • First observedtrends___get_top_trends

Related MCP Connectors

Related MCP Servers

  • AMZScout Skill + MCP

    amzscout-corp
    A
    license
    Not graded
    quality
    B
    maintenance
    AMZScout Skill + MCP gives AI agents live access to real Amazon marketplace data across 14 Amazon marketplaces. Analyze any ASIN, validate product ideas, research niches, compare competitors, discover profitable keywords, and build data-driven PPC strategies using trusted Amazon insights instead of AI assumptions. Works with Claude, ChatGPT, Cursor, and any other MCP-compatible AI client.
    1
    MIT

  • Google Trends MCP

    trendsmcp-ai
    A
    license
    A
    quality
    C
    maintenance
    Enables AI agents to query live trend data and historical search volume across 30+ platforms like Google, TikTok, YouTube, Amazon, and Reddit, including growth comparisons and top-ranking trends.
    3
    16
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources