Retail media teams often look for ways to connect category demand, commerce search, and news spikes into the same AI thread. Trends MCP supplies normalized trend pulls and live leaderboards so planners can brief retail networks without rebuilding a custom data stack.
Retail media sits between retailer first-party audiences and open market attention. Buyers expect proof that a category is rising before they fund onsite packages, sponsored search adjacency, or co-branded video. Generic articles about marketing MCP servers rank because they promise fewer exports. This page narrows that promise to commerce-led signals your assistant can fetch as structured series instead of pasted screenshots.
Start with Google Search growth on the category head term, then add Google Shopping for the same phrase to see if purchase intent language diverges. Layer Amazon search trends on hero SKUs when the merchant cares about basket builders, not only awareness. If headlines are moving, add news volume on the category name and optional news sentiment on the sponsor brand. Close with TikTok hashtag history when the brief demands short-form proof. Trends MCP returns structured points so the model can sort winners without manual CSV merges.
When a stakeholder asks what is selling right now, get_top_trends can return Amazon Best Sellers by Category, App Store or Google Play charts for companion apps, or Google Trends for macro search spikes. The feed labels are case sensitive, so copy them from the documentation. Leaderboards are a snapshot; pair them with get_growth when the deck needs a directional story across months.
Parallel rises on TikTok and flat curves on Google Search can mean culture-led buzz without search volume yet. The opposite pattern can mean search demand without a viral hook. Trends MCP reports how series move together; causal proof still needs separate validation. Teams should write that limit into client footnotes, especially for YMYL categories where regulators watch claims.
Free accounts include 100 monthly requests. Plan one batched prompt per major category instead of repeated pulls with tiny edits. Upgrade paths and paid caps live on the public pricing page. For exact numbers, read the current plan table at https://www.trendsmcp.ai/pricing.
Ask for explicit tool routing with using TrendsMCP. Keep keywords concrete ("gluten free frozen pizza") instead of vague themes. When comparing platforms, request separate sources in separate calls so each series keeps clean provenance. That habit makes audit trails easier when a network partner asks how a chart was built.
Tools for this workflow
get_trendsStack Google Search against Google Shopping for the same category phrase to see whether demand lives in generic search or purchase-ready shopping language.
get_trends(keyword='air fryer', source='google shopping')get_growthCompare 3M and 12M growth for a sponsor category cluster before committing network takeovers or seasonal packages.
get_growth(keyword='air fryer', source='amazon', percent_growth=['3M', '12M'])get_top_trendsPull Amazon Best Sellers by Category when a merchant asks what is moving inside Electronics or Home Kitchen this week.
get_top_trends(type='Amazon Best Sellers by Category', limit=25)FAQ