Integrations

get_reviews in ChatGPT

ChatGPT calls get_reviews after Trends MCP is added as a plugin on chatgpt.com. The proving call is a store listing, not a trending board.

Live data as of 2026-11-14

ChatGPT pulls store reviews through Trends MCP get_reviews after the plugin is added on chatgpt.com. The homepage fetched 2026-11-14 tells operators to open Plugins, pick Add custom MCP server, paste https://www.trendsmcp.ai/mcp, choose OAuth, create the plugin, install it, and type @ to pick Trends MCP. llms-full.txt from the same morning matches that www host and OAuth recipe. The dedicated Trends MCP for ChatGPT page, last updated 2026-08-19, still tells operators to add https://api.trendsmcp.ai/mcp with a Bearer key under Settings, Connectors. Ask, using TrendsMCP, for source App Store, Google Play, or Amazon plus a brand, app, product, or place name. Omit limit and both App Store and Google Play still print count 10 over window_days 90.

Plugins still want www OAuth, not a Bearer key

Host setup for ChatGPT lives on Trends MCP for ChatGPT. That page, last updated 2026-08-19, still proves the connect with get_trends, get_growth, and get_ranked_trends, and it still publishes the api host plus a Bearer header. This page is the review-shaped call that guide never names, against the recipe the homepage publishes today.

The homepage fetched 2026-11-14, under Add to ChatGPT, prints these steps:

  1. Click Add to ChatGPT. In Plugins, select +, then Add custom MCP server.
  2. Name it Trends MCP, paste the server URL, and choose OAuth. Accept the warning and select Create as a plugin.
  3. Install it and sign in to Trends MCP. In a chat, type @ and pick Trends MCP.

The URL on that card is https://www.trendsmcp.ai/mcp. The same homepage groups ChatGPT with Claude as a sign-in client on that www host. Cursor and VS Code stay on the api host with a Bearer key. llms.txt last updated 2026-11-14 repeats the split: "MCP, sign in (Claude, ChatGPT): https://www.trendsmcp.ai/mcp. No key to paste."

OpenAI's custom MCP server guide, fetched 2026-11-14 from https://developers.openai.com/api/docs/guides/custom-mcp-server, matches the homepage path. Access is ChatGPT on the web. The add flow is ChatGPT Plugins, the plus button, Add custom MCP server, a public HTTPS URL, then authentication. The listed auth options are OAuth, no authentication, and mixed OAuth or no authentication. Create as a plugin. Install it. Type @ in the prompt box and select the installed plugin. This run did not click Add to ChatGPT and did not complete OAuth in a ChatGPT tab. It recorded the published steps.

The dedicated ChatGPT page still says Settings, Connectors, Add custom connector, Server URL https://api.trendsmcp.ai/mcp, and Authorization: Bearer YOUR_API_KEY. That is the Cursor shape. It is also the shape OpenAI's plugin form does not list. Do not paste Cursor's url plus headers object into the ChatGPT plugin dialog. get_reviews in Cursor uses that JSON. Pasting it into Plugins is the wrong host.

Do not paste Claude Desktop's npx mcp-remote block either. get_reviews in Claude keeps that file on Desktop. A ChatGPT plugin is not a claude_desktop_config.json edit.

Homepage copy fetched 2026-11-14 also says the plugin works in ChatGPT on the web, and that on Business and Enterprise a workspace admin can turn custom servers off. That is OpenAI's workspace, not the Trends MCP Business plan. Confirm the workspace allowlist includes www.trendsmcp.ai before blaming a missing tool list on the API key field that the current plugin form does not show.

Name get_reviews after the @ mention

OpenAI's guide says custom MCP plugins are used by typing @ and picking the installed plugin. The homepage repeats that @ step. A ChatGPT Project instruction can name get_reviews, sources App Store, Google Play, and Amazon, and a cap of one store then stop. It should not name this morning's review ids. Store rows turn over. A frozen review in a Project file becomes a stale architecture note.

Ask with "using TrendsMCP" so ChatGPT routes to the server instead of a web search or a remembered headline from training data. 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.

The dedicated ChatGPT page still tells the model to call get_trends and get_ranked_trends. The live MCP list in this session 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. get_ranked_trends is absent.

Nightly review tracking belongs on REST, not a ChatGPT loop that only runs when the chat is open. POST https://api.trendsmcp.ai/api with a Bearer key and mode get_reviews. Wrapping a ChatGPT thread in a shared link just to pull reviews is a roundabout way to hit that URL, and it still spends the connector owner's meter.

App Store omit-limit printed 10 today

A 2026-11-14 MCP get_reviews call that sent source App Store and keyword notion with no limit, days, or country field printed window_days 90, count 10, 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,688 ratings. Developer Notion Labs, Incorporated. Genre Productivity. Version 1.7.353. Storefront URL:

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

Rank 1 was review 14783049513, title "Always Require Update To Work", published 2026-11-12T21:16:36Z, 1 star, helpful 0, reply null. REST with limit 1 printed count 1 and that same id. Keyword 1232780281 pinned that same listing and left alternatives empty. Keyword notion filled three alternatives: Notion Calendar id 1607562761 (7,847 ratings), To-Do List & Tasks for Notion id 1594021892 (761), Widget for Notion id 6751851452 (41).

The 10-row window had summary.average_rating 2.2: five 1-star rows, two 2-star, one 3-star, zero 4-star, two 5-star. replied_share 0.0. negative_share 0.7. Rank 8, review 14767270789, carried helpful 1. The other nine rows in that window carried 0. Newest-first store rows are not the all-time histogram on subject.rating.

ChatGPT on App Store matched too, and this morning it also printed a review row. Keyword chatgpt with limit 1 returned subject.id 6448311069, rating 4.8 from 12,220,708 ratings, developer OpenAI OpCo, LLC, version 1.2026.307, and review 14783266611, title "All A's", 5 stars, published 2026-11-12T22:39:47Z. Alternatives included Google Gemini id 6477489729 (2,426,377 ratings), Grok id 6670324846 (1,605,353), and Claude by Anthropic id 6473753684 (303,695). Looking up ChatGPT reviews inside ChatGPT still returns Claude as a near-miss listing. That is not a reviews payload for Claude.

get_reviews in Cursor and get_reviews in Claude recorded count 0 for this same Notion id on 2026-11-09 and 2026-11-10, with error null. The get_reviews product page from 2026-11-08 printed 10 App Store rows, rank 1 review 14752198455. Today's rank 1 is a different id. An empty items array is still an answer. A filled array a few days later is also 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. Do not ask ChatGPT to retry App Store in a loop. One call already billed.

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-14. Subject was Notion: AI Workspace, package notion.id, rating 4.6 from 406,769 ratings. Alternatives included Notion Calendar (com.cron.calendar), Microsoft OneNote (com.microsoft.office.onenote), and Google Keep (com.google.android.keep). Read subject.id before averaging stars. A name search also returns near-misses.

The 10-row window had summary.average_rating 3.3: three 1-star rows, one 2-star, zero 3-star, two 4-star, four 5-star. replied_share 0.0. negative_share 0.4. Rank 1 was review cdaa50c3-34de-40d7-8e4e-9731e4cd6f52, author Sakariye, 1 star, published 2026-11-12T19:51:22Z, title null, extra app_version 0.6.4296. Rank 3, Elijah Coyoca, 5 stars, carried helpful 1. Rank 10, Lowkey, 5 stars, carried helpful 3. 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 1, Google Play count 1, and those same rank-1 ids. Top-level count is the sum of items, not the number of sources.

REST mode reviews with Google Play, keyword chatgpt, and limit 1 returned ChatGPT package com.openai.chatgpt, rating 4.8 from 68,361,491 ratings, and review 82c20d0f-cab4-4185-aa26-2c2565646fe0, 2 stars, published 2026-11-13T06:03:29Z, extra app_version 1.2026.307. Play alternatives on that lookup were Chatbot AI Assistant Genie, AI Chatbot Nova, and Perplexity.

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,621 ratings. summary.average_rating was null. insights.star_split was 5: 87, 4: 7, 3: 2, 2: 1, 1: 3. Topic Quality had 12,617 mentions, 10,618 positive, 1,999 negative. Leakage had 2,934 mentions, 790 positive, 2,144 negative. 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 listing is not the Amazon search index used on get_growth. See Amazon Trends API for the demand series.

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.

ChatGPT's MCP list dropped get_top_posts

The MCP tool list in this session, fetched 2026-11-14, 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/@treandsara/video/7705638158607682829, posted 2026-11-08, 2,100,000 plays, 122,600 likes. The same mode with keyword booktok returned https://www.tiktok.com/@thesocialgeekfamily/video/7705610160051457311, posted 2026-11-08, 1,800,000 plays, 314,300 likes. ChatGPT that reads the live MCP list will not offer that call. The existing get-top-posts-in-cursor and get-top-posts-in-claude pages still tell those hosts 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.

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.

OpenAPI 3.1 at https://www.trendsmcp.ai/openapi.json, fetched 2026-11-14, 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. It still contains one leftover get_top_posts comment describing a posts array. llms.txt, docs.md, pricing.md, and data-catalog.md last updated 2026-11-14 all name get_reviews.

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

Connecting is free. Calling is not. get_usage at the start of this run printed Business 6,095 of 25,000 used, then 6,107, 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.

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. Looping "until iOS reviews appear" finishes the free plan before the Project instruction is written.

Common questions

On chatgpt.com, open Plugins, select +, then Add custom MCP server. Name it Trends MCP, paste https://www.trendsmcp.ai/mcp, choose OAuth, create the plugin, install it, and type @ to pick it. Ask, using TrendsMCP, for get_reviews with source App Store, Google Play, or Amazon and a brand, app, product, or place name. Omit limit and Google Play still printed count 10 over window_days 90 on 2026-11-14.
The homepage and llms-full.txt fetched 2026-11-14 both put ChatGPT on https://www.trendsmcp.ai/mcp with OAuth and no key in the plugin form. The dedicated Trends MCP for ChatGPT page, last updated 2026-08-19, still publishes https://api.trendsmcp.ai/mcp with a Bearer key under Settings, Connectors. This run recorded both recipes and did not click Add to ChatGPT. Match the recipe to the UI that is actually open, then prove the connect with a reviews call.
A matched subject is not a frozen review list. On 2026-11-14, App Store for notion returned Notion Notes, Tasks, AI, id 1232780281, rating 4.8 from 90,688 ratings, count 10, and requests_charged 1. Rank 1 was review 14783049513, published 2026-11-12T21:16:36Z, 1 star. get_reviews in Cursor and get_reviews in Claude recorded count 0 on 2026-11-09 and 2026-11-10 with the same listing. Read subject before treating an empty list as a failed ChatGPT connect, and do not treat last week's empty window as a permanent cap.
The live MCP list in this 2026-11-14 session named get_time_series, get_growth, get_top_trends, get_context, get_reviews, and get_usage. It did not name get_top_posts. REST POST https://api.trendsmcp.ai/api with mode get_top_posts, source tiktok, keyword fitness, and limit 1 still returned HTTP 200 and a posts array. ChatGPT that reads the MCP tool list will not see that call.
Yes. POST https://api.trendsmcp.ai/api with mode get_reviews, or the alias reviews. An invalid mode payload on 2026-11-14 listed valid_modes as get_context, get_growth, get_reviews, get_time_series, get_top_trends. aliases named reviews and omitted get_context. OpenAPI 3.1 still has no GetReviewsRequest schema. Nightly review pulls belong on REST, not a ChatGPT loop that only runs when the chat is open.