get_top_trends country boards by ISO code

country on Trends MCP get_top_trends is an optional ISO 3166-1 alpha-2 filter for six live feeds: Google Trends, Google Trends by Category, YouTube Trending, TikTok Trending Hashtags, TikTok Trending Hashtags by Category, and X (Twitter) Trending. Omit it, or send an empty string, and the default United States board returns with no country field. Pass USA or United States and the same rows come back with the U.S. ISO code echoed. UK and United Kingdom echo GB. Germany echoes DE. Wikipedia, GitHub, Amazon, TikTok Trending Searches, and the other 18 types return HTTP 200 with statusCode 400 and error invalid_request. Unknown codes such as XX and ZZ 400 with a hint that names GB and JP. get_time_series and get_growth ignore an extra country field.

Omit country and the payload skips the field

A Google Trends call that sent only type on 2026-10-20 printed as_of_ts 2026-10-20T06:01:31.134365+00:00, limit 5, count 5, and no country key. Rank 1 was you can see everything. Rank 2 was tesla roadster. REST and MCP matched.

Pass the U.S. ISO code, USA, or United States and the rows stay put. The payload adds a country field with that two-letter code. The lowercase U.S. code did the same and kept the 06:01:31 stamp. The scheduled snapshot is the default board. The field appears only when a recognized country value is sent.

An empty string is omit. REST country "" on Google Trends returned that same 06:01:31 rank-1 row and still skipped the field.

GB is a different clock. MCP country GB printed as_of_ts 2026-10-20T06:04:17.279509+00:00, then 06:04:39 on a lowercase gb retry, then REST UK at 06:07:14.231089+00:00. Product copy says a missing country board is fetched live. Those later stamps are that fetch. The names moved with the code.

tesla roadster crossed three boards. pension credit did not. Rank 1 is not a global query. For the Google board without a country field, see the get_top_trends type contract.

JP printed Japanese-script queries and "country": "JP", as_of_ts 2026-10-20T06:04:20.613317+00:00. Rank 1 was the Kuril Islands query. Rank 2 was Typhoon 30. A first Japan alias call and a first FR call each returned count 0 and as_of_ts null, then retries filled. FR rank 1 on the filled pull was couvre feu at 06:06:24.509965+00:00. Live fetch can miss once. Read count and as_of_ts before treating an echoed code as a board.

Six feeds accept country. Eighteen return 400.

The 400 message is the allow-list. Wikipedia Trending with country GB returned HTTP 200, envelope statusCode 400, error invalid_request:

country is only supported for: Google Trends, Google Trends by Category, TikTok Trending Hashtags, TikTok Trending Hashtags by Category, X (Twitter) Trending, YouTube Trending

GitHub, Amazon Best Sellers Top Rated, and TikTok Trending Searches printed that same sentence. TikTok Trending Searches is a live feed. It is not one of the six. Do not copy country from a Hashtags call onto Searches.

The six that accepted the field on this pull:

Default YouTube Trending, no country, shared the 06:01:31 cluster. Rank 1 was Wanuga Tarugana(ft.Jah-Ben & Java Gee). GB rank 2 was a BBC trailer, Mortimer & Whitehouse: Gone Fishing Series 9 Trailer - BBC Trailers. JP YouTube at 06:05:51.483403+00:00 opened with MAZZEL / Touch -Music Video-. Same type, three boards.

Default TikTok Trending Hashtags at 06:01:31 ranked halloween, usa, nfl, meme, football. GB ranked tiktokmademebuyit, foryoudays, meme, tiktokmademebuylt, halloween. meme is the overlap. Rank 1 is not.

Google Trends by Category with category Games and no country ranked mw4, then ohio powerball winners october 17. The GB Games board kept mw4 at 1 and put bet365 at 3. TikTok Hashtags by Category Games moved rank 1 from pokemon on the default board to fc27 on GB. Category and country stack. Blank category still mixes boards; that mix is documented on the get_top_trends page, not here.

HTML /docs fetched 2026-10-20 has no country row in the get_top_trends request table. docs.md and llms.txt from the same day describe the field. OpenAPI 3.1 GetTopTrendsRequest has type, category, limit, offset, sort, and window. It does not have country. TopTrendsResponse does not list it either. Generated clients that follow the spec will not send the field. Live REST accepted it anyway, including alias top_trends with country DE.

Aliases fold to ISO codes

Product copy names USA and United States as aliases for the U.S. board. The 2026-10-20 pull also folded UK and United Kingdom to GB, Germany to DE, and Japan to JP. Lowercase gb folded too, as did the lowercase U.S. code. REST USA echoed the two-letter U.S. code on the 06:01:31 Google Trends snapshot. REST UK echoed GB on the live GB board.

Unknown values fail. XX and ZZ both returned invalid_request and Unknown country plus a hint that names three example codes:

Unknown country 'XX'. Use an ISO 3166-1 alpha-2 code such as US, GB, JP.

That hint is not the six-feed list. A bad code and a bad type are different 400s.

get_time_series and get_growth are not this filter. REST get_time_series for nike on google search with extra country GB returned 261 weekly points, first date 2021-10-23, value 65, volume 24804598. REST get_growth for the same keyword with extra country DE and percent_growth ["7D"] returned growth -3.64, recent 53.0 on 2026-10-17 versus 55.0 on 2026-10-10. Neither payload included a country key. The homepage Google Trends FAQ still describes country codes as a geo cut on search interest. That text does not match these two tools. Put country on get_top_trends.

Live-fetched boards skip rank_change snapshots

Default Google Trends sort rank_change, window 7d, limit 3 on 2026-10-20 printed as_of_ts 2026-10-20T06:01:31.134365+00:00, baseline_ts 2026-10-13T02:01:46.905971+00:00, and count 2. Rows were objects: visionquest at rank 39, prev_rank 151, rank_change 112; then 2028 democratic primary frontrunners harris at rank 71, prev_rank 133, rank_change 62. The explicit U.S. country call matched those two rows and added the echoed code.

GB did not. MCP and REST both returned:

{
  "as_of_ts": null,
  "type": "Google Trends",
  "limit": 3,
  "offset": 0,
  "count": 0,
  "data": [],
  "country": "GB",
  "baseline_ts": null,
  "sort": "rank_change",
  "window": "7d",
  "note": "No snapshots available for 'Google Trends'."
}

YouTube Trending country GB with the same 7d movers call printed No snapshots available for 'YouTube Trending'. Count 0. This note is not the monthly Top Websites Retry with window="30d" text on the pagination page. A live-fetched country board has a current rank list and no baseline. sort rank on GB Google Trends filled five rows the same morning. Movers need history the live fetch does not store.

X country boards are not one clock

Omit country on X (Twitter) Trending and the 2026-10-20 pull still served as_of_ts 2026-09-30T18:01:51.542942+00:00. Rank 1 was Flydubai. Rank 4 was the string Unites States. Explicit U.S. country echoed the code and kept that stamp. The Google Trends default board that morning was 2026-10-20. The X default board was 20 days behind.

GB and DE on X returned count 0, data [], as_of_ts null, and "country": "GB" or "DE". MCP and REST agreed. Echoed country is not a filled board.

JP on X filled five rows. MCP stamped 2026-10-20T06:05:38.998813+00:00. REST stamped 2026-10-20T06:07:28.713601+00:00. The REST strings arrived as Latin-1 mojibake of UTF-8. Decoded they were 土田さん, イケメン大会, a Familymart chocolate-bread hashtag, a music-and-work hashtag, and サイゾウ. Rank on that JP board is not the Flydubai row. Do not join X country codes on as_of_ts. For the default X chart without a country field, see the X (Twitter) Trending API.

YouTube Trending without country used the 06:01:31 cluster. YouTube GB and JP used later live stamps. TikTok Hashtags did the same split. Read the stamp per type and per country. The YouTube Trending API page is the feed without this filter.

Exact country calls

MCP tool name is get_top_trends. REST mode is get_top_trends (alias top_trends). One type per call. country is optional and only valid on the six feeds in the 400 list. limit still defaults to 25. offset still defaults to 0.

{
  "mode": "get_top_trends",
  "type": "Google Trends",
  "country": "GB",
  "limit": 5
}

{
  "mode": "get_top_trends",
  "type": "Google Trends",
  "country": "USA",
  "limit": 5
}

{
  "mode": "get_top_trends",
  "type": "YouTube Trending",
  "country": "JP",
  "limit": 5
}

{
  "mode": "get_top_trends",
  "type": "Wikipedia Trending",
  "country": "GB",
  "limit": 3
}

REST transport is HTTP 200 even when the envelope statusCode is 400. The omit-type body on 2026-10-20 was HTTP 200 / statusCode 400 / error invalid_request, message starting The 'type' parameter is required. plus 24 feed names. Product docs still call that failure missing_parameter. Country errors use invalid_request too. Read the live error field.

Product docs bill a successful get_top_trends call as 1 REST request, or on MCP as 1 credit per 10 requested rows with a max of 10 credits. Extra country does not change that rule. Failed 4xx envelopes do not count. Free is 100 requests per month. Starter is $19 for 1,000. Check current pricing before locking a budget.