Plan free-tier Trends MCP API budgets

How does request counting change a design doc?

Document the exact payloads before coding. Get Trends and Get Growth both hinge on one source plus keyword pair per billable unit, while Get Top Trends multiplies by feed type and pagination. That distinction matters when a cron job loops across ten feeds each hour. API orchestration trend data outlines larger automation patterns.

What is a safe weekly cadence on the free tier?

Assume four weekly jobs. Each job can run get_growth on eight keywords across Google Search if each keyword uses one call with four presets bundled. That is thirty-two units. Add eight get_top_trends pulls for two feeds twice a week and the total lands under eighty units, leaving slack for manual debugging. Adjust when marketing adds more keywords.

How should agents phrase MCP prompts to avoid duplicate pulls?

Instruct assistants to include "Using TrendsMCP" once per task and to reuse cached JSON attached to the thread. Without that habit, chatty agents may repeat identical get_trends calls. Trends API free summarizes what ships on the unpaid tier for stakeholders who do not read code.

Where do Cursor and Python clients share logic?

Keep a tiny module that wraps POST https://api.trendsmcp.ai/api with the bearer header so both Cursor MCP configs and server-side cron jobs call the same function. The reference snippets on Python trends API mirror the JSON contract documented in the public docs, which reduces drift between environments.