Pass source google shopping for commerce demand, or source google images for visual demand. There is no Shopping or Images live board.
Live data as of 2026-09-22
A google shopping vs google images comparison on Trends MCP is two keyword sources on get_growth and get_time_series. Source google shopping returns a 0-100 commerce-demand series for any phrase. Source google images returns a 0-100 visual-demand series for the same phrase. There is no get_top_trends type for Shopping or Images. From the September 22, 2026 Google Trends board (as_of 2026-09-22T06:01:41 UTC), rank 3 was ed sheeran and rank 21 was converse ad. Dedicated get_growth closed nike at index 23.0 on google shopping and 53.0 on google images for recent_date 2026-09-19. The shopping series peaked at 100.0 on 2026-05-16 while images sat at 50. type Google Shopping is a 400. type google search aliases to Google Trends.
The September 22, 2026 Google Trends board is the split that still matters next month: live rank is a web-search title list, google shopping can sit far below google images on a brand, and the two series can peak years apart. Omitting limit returned limit 25, count 25, offset 0, as_of_ts 2026-09-22T06:01:41.162893+00:00. Rank 1 was how do i register to vote. Rank 3 was ed sheeran. Rank 21 was converse ad.
| Token | Trends rank | google shopping 7D | google images 7D |
|---|---|---|---|
| nike | off-board | 23.0 from 28.0, -17.86% | 53.0 from 56.0, -5.36% |
| ed sheeran | 3 | 23.0 from 7.0, +228.57% | 1.0 from 1.0, 0.0% |
| converse | 21 as converse ad | 20.0 from 23.0, -13.04% | 38.0 from 37.0, +2.7% |
| air fryer | off-board | 6.0 from 9.0, -33.33% | 7.0 from 9.0, -22.22% |
| spiderman | off-board | 34.0 from 36.0, -5.56% | 42.0 from 47.0, -10.64% |
Live rank is not a sort of either index. nike was off the board and still printed the cleanest brand split: shopping 23.0, images 53.0, same recent_date 2026-09-19, both 261-week series from 2021-09-25. converse ad sat at rank 21. The follow-up keyword was converse, not the full board string, and that name closed images 38.0 ahead of shopping 20.0, with uptrend_ratio 1/2 because images rose while shopping fell.
The inverse peak is the durable join. get_time_series on google shopping for nike returned 261 weekly rows from 2021-09-25 (index 58) to 2026-09-19 (index 23). Peak 100.0 landed on 2026-05-16. google images on that same week sat at 50. The week before, 2026-05-09, shopping was already at 93 while images sat at 43. The images series then closed its own peak at 100.0 on 2022-12-24, when shopping sat at 58. 12M on shopping was 23.0 from 27.0, -14.81%. 12M on images was 53.0 from 54.0, -1.85%. YTD on shopping was 23.0 from 27.0 on 2026-01-03, -14.81%. YTD on images was 53.0 from 53.0, flat.
1W matched 7D exactly on nike shopping: 23.0 from 28.0, -17.86%. 14D matched 2W: 23.0 from 32.0 on 2026-09-05, -28.12%. 1M matched 30D: 23.0 from 29.0, -20.69%. 1Y matched 12M. REST omitting percent_growth on google shopping defaulted to 12M and printed 23.0 from 27.0, -14.81%, 261 points. The same omit on google images defaulted to 12M and printed 53.0 from 54.0, -1.85%.
ed sheeran is the celebrity check, not the brand check. Shopping closed 23.0 from 7.0 on 7D, +228.57%, then 23.0 from 21.0 on 30D, +9.52%, then 23.0 from 33.0 on 12M, -30.3%. Images closed 1.0 from 1.0 on 7D, 1.0 from 4.0 on 30D, -75.0%, and 1.0 from 1.0 on 12M. The shopping series peaked at 100.0 on 2021-10-30 and printed 0 on many later weeks, including 2026-09-05, then 7.0, then 23.0. Quote 23.0 next to 1.0. Do not treat a sparse merch series as a second Google Trends rank.
Two strings, one tool family. REST uses mode get_growth or get_time_series. MCP uses the matching tool names. Commerce windows live on the Google Shopping trends API. Image windows live on the Google Images trends API. Window defaults live on get-growth. The search-versus-shopping split is documented with google search vs google shopping.
{"mode": "get_growth", "source": "google shopping, google images", "keyword": "nike", "percent_growth": ["7D", "30D", "12M", "YTD"]}
{"mode": "get_growth", "source": "google shopping", "keyword": "nike", "percent_growth": ["7D", "1W", "14D", "2W", "30D", "1M", "12M", "1Y", "YTD"]}
{"mode": "get_time_series", "source": "google shopping", "keyword": "nike"}
{"mode": "get_time_series", "source": "google images", "keyword": "nike"}
{"mode": "get_top_trends", "type": "Google Trends"}
The MCP equivalents are get_growth(keyword="nike", source="google shopping, google images", percent_growth=["7D", "30D", "12M", "YTD"]), get_time_series(keyword="nike", source="google shopping"), and get_top_trends(type="Google Trends"). REST top_trends with type Google Trends and limit 3 on September 22, 2026 returned the same snapshot timestamp as the omitted-limit MCP pull, with count 3: how do i register to vote, lizzie borden, ed sheeran.
The comma-separated nike call returned sources_requested ["google shopping", "google images"], sources_successful 2, and trend_analysis.uptrend_ratio 0/2 because both 7D directions printed decrease. volume_weighted_growth printed null, weight_coverage 0/2 sources, because neither close carried a volume field. Same preset, same recent_date 2026-09-19, different indexes: shopping 23.0, images 53.0.
get_time_series on google shopping, google images returned invalid_source with 16 names and no all. Multi-source strings belong on get_growth only. Source Google Shopping and source GOOGLE IMAGES both case-folded and returned HTTP 200, echoing google shopping and google images. Store the lowercase source strings.
air fryer stayed a quiet appliance on both indexes. Shopping closed 6.0 from 9.0 on 7D, -33.33%, and 6.0 from 11.0 on 30D, -45.45%. Images closed 7.0 from 9.0 on both 7D and 30D, -22.22%. 12M flipped: shopping 6.0 from 5.0, +20.0%; images 7.0 from 6.0, +16.67%. YTD then split: shopping 6.0 from 5.0, +20.0%; images 7.0 from 8.0 on 2026-01-03, -12.5%. 1W matched 7D and 1M matched 30D on both sources for that name.
get_top_trends with type Google Shopping returned HTTP 200 with envelope statusCode 400, error invalid_request, message Unknown type 'Google Shopping', plus 24 valid feed labels that include Google Trends and do not include any Shopping board. type google shopping failed the same way. type Google Images and type google images failed the same way. The handler did not map any of those four strings to the keyword sources.
type google search on get_top_trends returned HTTP 200 and echoed type Google Trends, with the same as_of_ts 2026-09-22T06:01:41.162893+00:00 and the same first five titles as the canonical label. llms.txt still describes feed labels as case-sensitive. The live handler accepted this lowercase alias on September 22, 2026. Prefer the canonical Google Trends spelling in stored configs. Do not store google search as a feed type just because it happened to alias, and do not expect google shopping to get the same mapping.
get_growth with source Google Trends and keyword nike returned HTTP 400, error invalid_source, message 'google trends' is not a valid source., plus 16 valid sources: google search, google images, google news, google shopping, youtube, wikipedia, tiktok, reddit, amazon, news sentiment, news volume, app downloads, app rankings, steam, npm, python, all. The handler lowercased the rejected source. It did not map it to google search or google shopping. The get_time_series reject list for a comma-separated pair is the same 16 names without all.
REST omitting type is a different 400. POST https://api.trendsmcp.ai/api with mode get_top_trends and limit 5, no type, returned HTTP 200 with envelope statusCode 400, error invalid_request, message The 'type' parameter is required, then the same 24-name list. llms.txt still names that miss missing_parameter. Read statusCode inside the JSON, not only the HTTP line.
nike is the volume check. A three-source get_growth on google search, google shopping, google images closed google search at 55.0 from 59.0 on 7D, -6.78%, volume_estimated true, recent_volume 20,900,000 from 22,500,000. volume_growth was omitted, with reason volume is derived from the trend value for this source, not an independent measurement. google shopping closed 23.0 from 28.0, -17.86%, with no volume fields. google images closed 53.0 from 56.0, -5.36%, with no volume fields. weight_coverage printed 1/3 sources and volume_weighted_growth -6.78, which is the search row only.
spiderman stayed a visual-and-merch name after the film window. Shopping closed 34.0 on 2026-09-19, 30D -38.18% from 55.0, 12M +47.83% from 23.0. Images closed 42.0, 30D -40.85% from 71.0, 12M +90.91% from 22.0. The shopping series peaked at 100.0 on 2021-12-25, then printed 85.0 on 2026-08-08, 66.0, 55.0, 48.0, 35.0, 36.0, 34.0. Images on this pull stayed ahead of shopping on every window. Quote 34.0 next to 42.0. Do not invent a shopping-unit count.
get_top_trends MCP pricing is 1 credit per 10 requested rows, max 10 credits per call. REST counts 1 request per call. Free boards still cap at the top 10. The 25-row Google Trends pull on this page is the paid default, which is also what the handler returns when limit is omitted on a paid key. Commerce follow-up is the Google Shopping trends API. This split stays inside Google: commerce demand versus visual demand for one phrase.
FAQ