Sheets stays the default place for cross-team numbers. Trends MCP returns dated JSON for growth and history so a small script can append rows without rebuilding scrapers each quarter.
Finance, growth, and editorial leads often want one workbook they can filter during a live call. Trends MCP focuses on normalized time series and growth windows across sources such as google search, youtube, tiktok, amazon, and news volume, which maps cleanly to columns when a short script handles transport. The approach mirrors how Make trend automation teams already schedule HTTP work, except Sheets becomes the warehouse of record for lightweight governance.
Read a small config range or JSON file listing tuples of source, keyword, and optional windows. For each tuple, POST to https://api.trendsmcp.ai/api with the Bearer key from trendsmcp.ai/account. Parse the body, then append or upsert rows. Stamp each batch with as_of_ts when the API returns it so stale tabs are obvious during Monday reviews.
Keep both normalized value and optional volume fields when the response includes volume. For get_growth results, store period, growth, direction, recent_date, baseline_date, recent_value, and baseline_value in adjacent columns. Resist merging everything into prose cells; numeric columns keep sparklines honest when someone duplicates the tab for a client copy.
A common layout is three tabs: long history from get_trends, rolling growth from get_growth, and a live seeds tab from get_top_trends for TikTok Trending Hashtags or Google Trends. Pivot tables can group by source when leadership wants one scoreboard without opening five vendor sites. The how to build a trends dashboard guide covers visualization choices when the same JSON also feeds a BI tool.
The public docs explain how calls count toward the monthly quota. Batching keywords per source inside a single run reduces surprise throttling. If a cell formula calls an external endpoint on every recalc, disable that pattern; instead, rely on time-driven triggers so accidental refreshes do not burn the key during a demo.
Row limits and audit trails eventually push teams toward BigQuery or Airtable. Airtable trends automation describes a worker-first pattern that still begins with the same JSON contract. Until that migration, Sheets plus a thin script keeps momentum data next to budget models without forcing analysts to learn a new UI overnight.
Interactive research still belongs in assistants. Claude and Cursor can call MCP tools for ad hoc comparisons, while Sheets stores the scheduled truth. Prompt writers should include phrasing such as "using TrendsMCP" so the model routes to tools instead of guessing from memory.
Teams that prefer Python notebooks or CI jobs can follow python trends API examples, then export CSV into the same workbook for leadership-friendly views. Programmatic SEO data pipeline covers how content ops teams chain keyword pulls into publishing systems when Sheets is only one stop in the chain.
FAQ