Four type values on get_top_trends take a category string. The MCP server in this session names them: Amazon Best Sellers by Category, Google Trends by Category, Top Websites, and Substack by Category. Without category those boards mix. The HTTP call is POST https://api.trendsapi.ai/api. Parse the string body. How to call a board is on get_top_trends. Official name tables sit on the category feeds reference.
Four types need the field
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json
{"mode":"get_top_trends","type":"Google Trends by Category","category":"Games","limit":10}
Google Trends without by Category is a different type and does not take category. Substack without by Category is the unfiltered newsletter board.
Unknown names return an error that lists valid categories. Do not invent a slug.
Mixed board if omitted
A first pull with no category is a discovery call. Rows can include a category_path. That path is a hint for the next request, not a substitute for sending category. Production crons should pass the official string on every page, including paginated pulls.
Official names, not Explore IDs
Amazon matching is case-sensitive. Toys Games is the stored string. Google topics, Top Websites slugs, and Substack labels resolve case-insensitively to the stored form. Top Websites also accept a parent/child path such as finance/investing.
Do not send a numeric Google Explore category id. Pass category on every page of these four, including a rank_change sort. Climber sort is on rank_change sort. Caps stay on pricing.