get_context default limit, comments, and source rows

get_context on Trends MCP returns recent posts, videos, stories, repos, and prediction markets for one keyword. Valid sources are News, YouTube, TikTok, Instagram, X, Reddit, Bluesky, Hacker News, Polymarket, and GitHub. One call accepts at most five of those names. Omit limit and each source prints up to 10 items over a 7-day window. Max limit is 20. comments defaults to 2 and fills the first N items of sources that support replies, not N replies per row. REST mode is get_context. The alias context also works. Product docs, llms.txt, pricing.md, and OpenAPI fetched 2026-10-26 still say three tools. The live MCP list and REST valid_modes both include get_context.

Omit limit and each source still prints 10

From the Trends MCP pull of 2026-10-26, a get_context call that sent source YouTube and keyword nintendo switch 2 with no limit, days, or comments field returned window_days 7 and count 10. Rank 1 was YouTube id KuLxII__zqE, title "The Nintendo Switch 2 Replaced EVERYTHING For Me!", published 2026-10-25T14:00:10Z, 49,451 views, 1,086 likes, 202 comments. REST with the same body printed the same defaults. limit 1 printed count 1 and that same id.

The server does not share the get_top_posts default. That tool omits limit and prints 20, then 400s at 21. get_context max is also 20, but REST limit 21 on YouTube printed count 20. REST limit 0 printed count 1. MCP limit 21 printed count 20. Out-of-range values clamp here.

days clamps the same way. REST days 31 on News printed window_days 30 and count 1. MCP days 30 on YouTube with limit 1 succeeded. MCP days 31 on YouTube echoed window_days 30, then returned envelope statusCode 502 with source-level error source unavailable and count 0. Treat 30 as the ceiling. Do not treat a 31 as a documented 400.

offset is not a pager. REST offset 10 on News with limit 1 still printed the same GameSpot story as the unpaged News call. There is no second page in the payload. Lower limit if a shorter list is needed.

Top-level count is the sum of items across sources, not the per-source cap. A four-source call with limit 1 printed count 4. A five-source call with limit 2 printed count 6 because Polymarket and Hacker News returned zero rows for nintendo switch 2.

comments N fills items, not replies

The MCP schema says comments is "Top comments for the first N items of each source, 0 to 5. Default 2." The 2026-10-26 YouTube pulls matched that wording, not "N replies on every row."

Omit comments and videos 1 and 2 carried 3 top_comments objects each. Videos 3 through 10 carried []. comments 0 left every array empty, including rank 1. comments 5 filled the first 5 videos, still 3 replies each. comments 6 still filled 5. The server clamps to 5. It does not 400.

Comment objects in this pull had text, author, likes, and published. Rank 1's first reply was from @Jimtendo64 with 18 likes, published 2026-10-25T16:52:40Z. That shape is independent of limit. limit 21 with comments 0 returned 20 videos and empty arrays.

News, GitHub, and Polymarket rows left top_comments empty. The schema limits comments to YouTube, TikTok, Instagram, X, Reddit, Bluesky, and Hacker News. Passing comments 1 on a News-only call still returned stories with empty arrays. Set comments 0 when the job is titles and engagement only. That avoids fetching replies the source will not attach.

Six sources return too_many_sources

A comma list of six names, YouTube,TikTok,Reddit,News,GitHub,X, returned envelope statusCode 400, error too_many_sources, message At most 5 sources per call. llms.txt last updated 2026-10-26 still lists missing_parameter, invalid_source, invalid_mode, invalid_request, no_data, source_unavailable, growth_calculation_failed, and internal_error. It does not list too_many_sources. OpenAPI's Error.error enum matches that older table.

Five names succeeded. source News,Polymarket,GitHub,Bluesky,Hacker News with limit 2 printed five sources objects. News count 2, GitHub count 2, Bluesky count 2, Polymarket count 0, Hacker News count 0. The fifth official name is Hacker News with a space. REST HackerNews and hacker-news both returned 400 invalid_source with the ten-name list.

source google search returned 400 invalid_source, message Unknown source 'google search'. Valid: News, YouTube, TikTok, Instagram, X, Reddit, Bluesky, Hacker News, Polymarket, GitHub. That list is not the get_growth keyword index. youtube lowercase on REST echoed YouTube and returned the same rank-1 video. tiktok echoed TikTok. news echoed News. Case folds. The google search string does not.

Missing REST fields used missing_parameter, which matches the docs table. Omit keyword and the message is keyword is required: any name or phrase. Omit source and the message lists the ten names. Failed 400s are free per pricing.md. A successful multi-source call is the one that bills. The MCP tool description says 1 request per source. get_usage still prints other tools use 1. pricing.md last updated 2026-10-26 still omits get_context.

Row kind is video, story, repo, or market

get_context items share source, kind, id, url, title, text, author, published, engagement, top_comments, and extra. kind and engagement do not. The 2026-10-26 pulls printed this map:

News extra on the GameSpot cluster carried outlet_count 8, article_count 11, and an outlets list that included GameSpot, Nintendo Life, and Polygon.com. GitHub rank 1 for nintendo switch 2 was 0xNikilite/oboromi, 1,356 stars, language Rust, with a note no GITHUB_TOKEN: limited to 10 searches/minute. Polymarket on bitcoin returned kind market, event id 89502, volume_usd 78,329,631, and the note markets are not limited to the window; they are open events. Rank 1 there was published 2025-11-24T19:07:12Z, months outside the 7-day window.

Instagram can ignore the window too. nintendo switch 2 with limit 1 printed a reel at https://www.instagram.com/reel/DWZVvqLkYGM/, published 2026-03-27T17:20:37Z, 361,203 views, plus the note no reels in the last 7 days; showing the most relevant. Read notes before treating published as inside window_days.

Hacker News on nintendo switch 2 printed count 0. The same source on bitcoin printed two posts, rank 1 id 50224916, title "Show HN: Steal My Bitcoin", score 597. Empty is a miss for that keyword, not a dead source.

TikTok rank 1 was https://www.tiktok.com/@whistrey/video/7699816782852361502, 220,783 views, duration_s 68. X rank 1 was status 2114019332007039249 from @0x_kaero. Reddit rank 1 was /r/switch2 post t3_1xbsnjf, score 11, upvote_ratio 0.641. Those fields do not exist on YouTube rows. Parse per kind.

This is also not get_top_trends. That tool ranks a live feed with no keyword. get_context needs a keyword and never returns a board type.

REST lists five modes. OpenAPI still maps three.

POST https://api.trendsmcp.ai/api with this body returned the default YouTube 10 on 2026-10-26:

{"mode": "get_context", "source": "YouTube", "keyword": "nintendo switch 2"}

mode context with limit 1 returned the same rank-1 video. A garbage mode getcontext returned 400 invalid_mode and this list: get_context, get_growth, get_time_series, get_top_posts, get_top_trends. The aliases object on that error named aliases for the last four tools and omitted get_context, even though context had just succeeded.

OpenAPI 3.1 fetched the same morning still describes "one of three operations" and maps mode only to get_time_series, get_growth, and get_top_trends. GetTopTrendsRequest still omits country. HTML /docs grepped 0 hits for get_context, get_top_posts, and country. docs.md and llms.txt last updated 2026-10-26 still say three tools. pricing.md from that morning still bills get_time_series, get_growth, and get_top_trends only.

REST get_usage is not a mode. mode get_usage and usage both returned invalid_mode. Usage stays on the MCP get_usage tool. That payload printed Business 6,890 of 25,000 used at the start of this run, reset 2026-11-01, cost_rule get_top_trends uses 1 request per 10 rows; other tools use 1.

Call the endpoint. Do not treat the spec table as the tool list.