get_reviews in Cursor

Cursor Agent pulls store reviews through Trends MCP get_reviews after the Cursor object is saved at https://api.trendsmcp.ai/mcp with transport http and a Bearer key. Ask, using TrendsMCP, for source App Store, Google Play, or Amazon plus a brand, app, product, or place name. Omit limit and Google Play still prints count 10 over window_days 90. App Store can match the listing and still print items [] with error null. That empty array billed 1 request on 2026-11-09. The live MCP list in this session names get_reviews and does not name get_top_posts. REST mode get_top_posts still returned a TikTok row the same morning.

Cursor wants url plus transport, then get_reviews

Host setup lives on Trends MCP for Cursor. This page is the review-shaped call that host guide never names. Mac and Linux: ~/.cursor/mcp.json. Windows: %USERPROFILE%\.cursor\mcp.json. Under mcpServers:

"trends-mcp": {
  "url": "https://api.trendsmcp.ai/mcp",
  "transport": "http",
  "headers": {
    "Authorization": "Bearer YOUR_API_KEY"
  }
}

Key from the account page, format tmcp_live_. Fully quit Cursor. A window reload is not enough on every build. Homepage copy-config fetched 2026-11-09 still omits transport and can look pasted-complete:

{"mcpServers": {"trends-mcp": {"url": "https://api.trendsmcp.ai/mcp","headers": {"Authorization": "Bearer YOUR_API_KEY"}}}}

llms-full.txt from the same morning prints that same Cursor block without transport. How to connect Cursor to live trend data includes it. Cursor wants url plus transport http. Windsurf wants serverUrl. VS Code wants type http under servers. Claude.ai wants https://www.trendsmcp.ai/mcp for OAuth and will 401 in this file.

Ask with "using TrendsMCP" so Agent routes to the server instead of a web search. The proving prompt is a reviews call, not a board call.

get_reviews(source="Google Play", keyword="notion", limit=5)
get_reviews(source="App Store", keyword="1232780281", limit=5)

get_top_trends with type App Store Top Free still ranks charts. That is a different tool. Do not send a board type string into get_reviews. Do not send source YouTube into get_reviews. MCP source YouTube on keyword notion returned 400 invalid_source, message Unknown source 'YouTube'. Valid: App Store, Google Play, Amazon.

App Store can match Notion and still print zero reviews

A 2026-11-09 MCP get_reviews call that sent source App Store and keyword notion with no limit, days, or country field printed window_days 90, count 0, and requests_charged 1. The listing matched. subject.name was Notion: Notes, Tasks, AI. subject.id was 1232780281. subject.rating was 4.8 from 90,650 ratings. Developer Notion Labs, Incorporated. Genre Productivity. Version 1.7.352. Storefront URL:

https://apps.apple.com/us/app/notion-notes-tasks-ai/id1232780281

error was null. notes was []. summary.average_rating was null. items was []. REST with the same body printed the same empty array. MCP days 365 with limit 10 still printed window_days 365 and count 0. Keyword 1232780281 pinned that same id and left alternatives empty. Keyword notion filled three alternatives: Notion Calendar id 1607562761 (7,807 ratings), To-Do List & Tasks for Notion id 1594021892 (761), Widget for Notion id 6751851452 (40).

ChatGPT on App Store matched too. Keyword chatgpt returned subject.id 6448311069, rating 4.8 from 12,053,969 ratings, developer OpenAI OpCo, LLC, version 1.2026.300, and the same empty items array. Alternatives included Google Gemini id 6477489729 (2,411,148 ratings), Grok id 6670324846 (1,590,329), and Claude by Anthropic id 6473753684 (298,917).

The get_reviews page from 2026-11-08 printed 10 App Store rows for notion, rank 1 review 14752198455. That window is gone from this morning's payload. The listing is not. An empty items array is still an answer. get_usage cost_rule during this run: 1 request per data type in a call; get_top_trends: 1 request per 10 rows per board (limit defaults to 100). Only data types that answer are charged. Empty App Store items still charged 1.

Do not ask Agent to retry App Store in a loop. One call already billed. Switch source, or read subject.rating as the all-time store score and stop.

Google Play omit-limit still returns 10

MCP get_reviews with source Google Play and keyword notion, limit omitted, printed window_days 90, count 10, and requests_charged 1 on 2026-11-09. Subject was Notion: AI Workspace, package notion.id, rating 4.6 from 405,549 ratings. Alternatives included Notion Calendar (com.cron.calendar), Notion: Music Notation & Tab (com.presonus.notionmobile), and Microsoft OneNote (com.microsoft.office.onenote). The music app is a different product that shares the word. Read subject.id before averaging stars.

The 10-row window had summary.average_rating 3.7: two 1-star rows, zero 2-star, two 3-star, one 4-star, five 5-star. replied_share 0.0. negative_share 0.2. Rank 1 was review 7c31caf4-9f30-4042-82d5-af4b8c5f3230, author Ale P, 4 stars, published 2026-11-07T22:03:42Z, title null, helpful 0, extra app_version 0.6.4288. Rank 4, Richard Fisher, 3 stars, carried helpful 2. The other nine rows in that window carried 0. Play rows in this pull left title empty. reply was null on every Play row here.

A comma list billed both stores. source App Store, Google Play with limit 1 printed requests_charged 2, App Store count 0, Google Play count 1, and that same Play review id. Top-level count is the sum of items, not the number of sources.

Amazon is the third review source. Keyword B0CJZMP7L1 matched STANLEY Quencher H2.0 Flow State Tumbler, 30 oz, Lilac, brand STANLEY, rating 4.7 from 207,985 ratings. summary was null. insights.star_split was 5: 87, 4: 7, 3: 2, 2: 1, 1: 3. The one item had kind excerpt, id B0CJZMP7L1:Quality:0, rating null, published null. The source note was Amazon shows excerpts and topic counts without sign-in, not full dated reviews; days does not filter them. That is not the Amazon search index used on get_growth.

get_context takes conversation sources such as YouTube, News, or Reddit. Those names are invalid_source here. Use get_reviews when the job is what customers wrote on a store page.

Cursor MCP no longer lists get_top_posts

The MCP tool list in this session, fetched 2026-11-09, advertised get_time_series, get_growth, get_top_trends, get_context, get_reviews, and get_usage. Six tools. Five of them bill. get_usage is free. get_top_posts is absent.

REST still serves the old posts mode. POST https://api.trendsmcp.ai/api with mode get_top_posts, source tiktok, keyword fitness, and limit 1 returned HTTP 200, count 1, and https://www.tiktok.com/@lizzie.ramey/video/7702902040111992095, posted 2026-10-31, 1,200,000 plays, 136,200 likes. Cursor Agent that reads the live MCP list will not offer that call. The existing get-top-posts-in-cursor page still tells Agent to call it.

A garbage REST mode getreviews returned envelope statusCode 400, error invalid_mode, and valid_modes get_context, get_growth, get_reviews, get_time_series, get_top_trends. The aliases object named reviews for get_reviews. It named aliases for get_time_series, get_growth, and get_top_trends. It omitted get_context. REST mode reviews with Google Play, keyword chatgpt, and limit 1 returned ChatGPT package com.openai.chatgpt, rating 4.8 from 67,724,102 ratings, and review ad0c0d3a-d9ff-4baf-b486-ad8369b608db, 5 stars, published 2026-11-08T06:03:50Z.

Omit REST source and the message is source is required: one or more of App Store, Google Play, Amazon (comma-separated). Omit keyword and the message is keyword is required: a brand, app, product or place name. Failed 400s are free. A successful multi-source call is the one that bills.

Nightly review tracking belongs on REST, not an Agent loop that only runs when Cursor is open. Connecting is free. Calling is not. get_usage at the start of this run printed Business 2,393 of 25,000 used, then 2,406, reset 2026-12-01. buy_credits_url on that payload still uses the apex account billing tab:

https://trendsmcp.ai/account?tab=billing

Site links on this page stay on www.

OpenAPI names get_reviews and still skips the schema

OpenAPI 3.1 at https://www.trendsmcp.ai/openapi.json, fetched 2026-11-09, describes five tools in the path text, including get_reviews at 1 request per source. Request examples include a Get Reviews body with keyword notion and source App Store. components.schemas still has no GetReviewsRequest and no reviews response type. The mode discriminator mapping lists get_context, get_growth, get_time_series, and get_top_trends only. The 200 example set omits a reviews payload. HTML /docs grepped 9 hits for get_reviews and 0 for GetReviewsRequest. llms.txt, docs.md, pricing.md, and data-catalog.md last updated 2026-11-09 all name the tool.

A generated client that only emits the OpenAPI oneOf will never send get_reviews. Cursor Agent that reads the live tool list will. Wire the tool the host advertised in MCP, not the discriminator map.

Free plan 100 requests a month. Starter $19 for 1,000. Pro $49 for 5,000. Business $199 for 25,000. One Play call plus one App Store call is two requests even when App Store prints zero rows. Looping "until iOS reviews appear" finishes the free plan before the ticket is written.