mcp-google-merchants
Connect to Google Merchant Center and inspect or deliberately change account data, products, data sources, promotions, reports, and quotas.
Authenticate and manage the Google OAuth connection (status, setup instructions, save client, start/finish login, logout).
Inspect Merchant Center accounts, homepage claim status, and shipping settings.
Read processed products and diagnose product issues/disapprovals.
Run MCQL reports for performance, price competitiveness/insights, best sellers, and competitive visibility.
List, get, and create API data sources; trigger re-fetch of file or Google Sheets feeds.
Insert/replace, update, or delete product inputs in API data sources.
Create/update, list, and check approval status of promotions.
Check API quota usage and make raw Merchant API requests, including potentially destructive operations.
Allows managing Google Merchant Center products, promotions, data sources, and running MCQL reports via the Merchant API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-google-merchants Why is product sku-123 disapproved in Shopping ads?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Google Merchant Center MCP
English | Русский
A1 Google Merchant Center MCP connects an AI app to your Google Merchant Center account. Find out why products are disapproved, inspect feeds and promotions, explore reports and market prices, then make deliberate changes to product data when you need to.
It works with the Merchant Center data behind Shopping listings: products, data sources, promotions and reports. Campaigns, budgets and bids belong to Google Ads and are outside this server.
22 tools. 15 operations only read Merchant Center data; 5 write product, data-source or promotion data; 2 are potentially destructive.
Your Google access. The server uses your OAuth credentials and the Merchant API v1 — it does not create a separate Merchant Center account.
Source-aware changes. Product and promotion inputs can be changed only through an API data source. A file feed can be re-fetched, but its contents are not edited here.
Visible boundaries. Tools carry read-only, write or destructive metadata, so an AI client can distinguish an inspection from a live change.
Start with a read-only question:
Which products are disapproved, and what issues does Google report for each?
Connect the server · Explore use cases · Open technical documentation
See it work in a minute
You: Which products are disapproved, and what issues does Google report for each?
Assistant: Lists the affected products and explains the item-level issues that Merchant Center reports.
You: Show the current price and availability of product
SKU-123, then prepare an availability update toin_stock.Assistant: Shows the current product input, the API data source it belongs to and the exact change to make. It asks for confirmation before updating the live product input.
You: Confirm the update.
Assistant: Sends the update and explains that Merchant Center processes product data asynchronously. The processed product and its quality status can take several minutes to refresh.
Related MCP server: gmc-mcp
Contents
Quick start
You need Node.js 20+, a Google Merchant Center account and a Google Cloud project registered with Merchant Center. OAuth credentials are not required at install time — the server connects from the conversation, see Getting access.
Add the server to your AI app using one of the instructions below.
Say "connect Google Merchant Center": the assistant walks you through the OAuth client and the browser consent, no config files and no restart.
Ask the first read-only question above.
In the app:
Open Settings → MCP servers.
Select Add server.
Choose STDIO, then enter the launch command
npx -y mcp-google-merchants@latestand the four environment variables below.
Variable | Value |
| Your Google OAuth client ID |
| Your Google OAuth client secret |
| Your Google OAuth refresh token |
| Your Merchant Center account ID |
Select Save, then Restart.
From the command line:
codex mcp add google-merchants \
-- npx -y mcp-google-merchants@latestCheck the connection:
codex mcp listclaude mcp add \
--transport stdio \
--scope user \
google-merchants \
-- npx -y mcp-google-merchants@latestCheck the connection:
claude mcp listThe current official path is Settings → Extensions. For a custom desktop extension, open Advanced settings → Extension Developer → Install Extension…, select a .mcpb file and follow the prompts.
This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:
{
"mcpServers": {
"google-merchants": {
"command": "npx",
"args": ["-y", "mcp-google-merchants@latest"]
}
}
}In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.
Claude Desktop MCP documentation
Add a user-level server to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:
{
"mcpServers": {
"google-merchants": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-merchants@latest"]
}
}
}Run MCP: Open User Configuration from the Command Palette and add:
{
"servers": {
"google-merchants": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-merchants@latest"]
}
},
"inputs": [
{
"type": "promptString",
"id": "google_merchants_client_id",
"description": "Google OAuth client ID"
},
{
"type": "promptString",
"id": "google_merchants_client_secret",
"description": "Google OAuth client secret",
"password": true
},
{
"type": "promptString",
"id": "google_merchants_refresh_token",
"description": "Google OAuth refresh token",
"password": true
},
{
"type": "promptString",
"id": "google_merchants_account_id",
"description": "Merchant Center account ID"
}
]
}Check the server with MCP: List Servers.
What you can ask it to do
Find and understand catalog problems
Which products are disapproved, and what does Google report for each of them?
Show the title, price, availability and current status of product
SKU-123.Which products are out of stock?
Show the most frequent product issues for this Merchant Center account.
Explore performance and prices
Show clicks and impressions by product for July.
Which products are priced above the market benchmark in the United States?
What prices does Google suggest, and what impact does it predict?
Price comparisons and suggestions require the free Market Insights opt-in in Merchant Center. If the account has not opted in, the server explains why the report has no rows.
Inspect the account and feeds
List the Merchant Center accounts I can access.
Is the store homepage claimed? Show the current shipping settings.
List the product and promotion data sources, and identify an API data source.
Re-fetch this scheduled file feed now.
Make deliberate changes
Update the price and availability of this product in its API data source.
Create an API data source for a new product feed.
Create or update a promotion and then check its approval status.
For any request that changes data, first ask the assistant to show the target account, data source and exact fields it plans to change.
How Merchant Center data is connected
Merchant Center keeps the incoming data and the resulting product status separate:
An account contains product and promotion data sources.
A data source can be an API source, a file, a Google Sheet, the Merchant Center interface or an automatic feed.
A product input is the product data supplied by one source.
A processed product is what Merchant Center derives after processing that input. It includes eligibility and item-level issues.
The server can read every listed source type. It can create API data sources and update product inputs only in an API data source; it cannot write into a file, interface or automatic feed. To find products by condition, use a report query: list_products itself does not provide server-side filtering.
What can change
Operation | What happens | Confirmation boundary |
Inspect accounts, products, feeds, promotions, reports, issues and quota use | Reads data from Merchant Center | Does not change Merchant Center |
Create an API data source | Adds a source for product or promotion data | Changes the account |
Update a product input | Changes selected product fields, such as price or availability | Changes live source data |
Insert a product input | Replaces the complete input with the same ID in that API source; using a different source moves the product | Changes live source data |
Re-fetch a file feed | Requests an out-of-schedule fetch of a file or Google Sheets feed | Starts asynchronous work at Google |
Insert or update a promotion | Creates or changes a promotion | Changes live source data |
Delete a product input | Removes the input from the selected data source | Destructive |
Raw Merchant API request | Can access API methods without a dedicated tool | Potentially destructive |
The MCP client decides how it asks you to confirm write and destructive tools. The server marks its read-only, write and destructive operations so the client can present the right boundary.
Getting access
The server uses the Google Merchant API and the OAuth scope https://www.googleapis.com/auth/content. There are two ways to hand it credentials, and the first one needs no configuration files.
Connect from the chat (recommended)
Say "connect Google Merchant Center" and the assistant runs the flow with you:
setup_instructionsprints the checklist: create or select a Google Cloud project, enable Merchant API, configure the consent screen and create a Desktop app OAuth client.Download that client's JSON ("Download JSON") and give the assistant its path —
set_clientstores it owner-only. The secret never goes through the conversation.start_loginreturns a Google consent link. Open it on this machine and approve; the code comes back to a one-shot listener on127.0.0.1(PKCE), never through the chat.finish_loginexchanges the code, saves the tokens to~/.config/mcp-google-merchants/credentials.json(mode 0600) and verifies them with a real Merchant API call — so a project that is not registered with Merchant Center yet is caught right there.
The tokens are re-read on every call, so the connection works immediately — no restart of the AI app. auth_status shows what is connected, logout revokes and deletes it. The Cloud-project registration below is still required: it is a Merchant Center step, not an OAuth one.
Environment variables (CI, unattended installs)
Create or select a Google Cloud project, enable Merchant API, and configure the OAuth consent screen.
In Google Cloud, create an OAuth client of type Desktop app. Save its client ID and client secret.
Authorize the Google account that has access to your Merchant Center and obtain a refresh token for the scope above. The OAuth 2.0 Playground can help with this step: enable Use your own OAuth credentials, enter the scope, authorize, then exchange the code for tokens.
Find your Merchant Center account ID in Merchant Center and use it as
GOOGLE_MERCHANTS_ACCOUNT_ID.Register the Google Cloud project with Merchant Center once. Google requires a production Merchant Center account with a verified website and an account administrator for this operation. The registration links one Cloud project to the Merchant Center account; until it is complete, Merchant API calls from that project are blocked. Follow Google’s developer registration guide.
The one-time registration is available through the technical raw_request tool, but it is safer to follow Google’s guide if this is your first Merchant API setup. Google may take up to five minutes to accept calls after registration.
Treat the OAuth client secret and refresh token as passwords. They are kept in the MCP client configuration and can grant access to the Merchant Center account.
Configuration
Variable | Required | Description |
| No* | OAuth 2.0 client ID. |
| No* | OAuth 2.0 client secret. |
| No* | OAuth refresh token with the Merchant API scope. |
| No* | Short-lived access-token alternative to the three OAuth values above. |
| No | Default Merchant Center account ID. Individual requests can select another accessible account. |
| No | Fixed loopback port for the in-chat login; useful over SSH port forwarding. |
| No | Merchant API base URL override. |
| No | OAuth token endpoint override. |
| No | Per-request timeout in milliseconds; default is |
| No | Maximum retry count for temporary failures; default is |
* Use either the client ID, client secret and refresh token together, or a pre-minted access token. An access token usually expires in about one hour; a refresh token lets the server obtain a new access token when needed.
Data and telemetry
The server runs locally as a process started by your AI app. It sends Merchant Center requests to Google and refreshes OAuth access tokens through Google’s OAuth endpoint.
It sends anonymous usage telemetry to count active installations and tool demand: a random installation ID, package version, AI client and Node.js/operating-system versions, and the tool name. It never sends or stores OAuth tokens, Merchant Center data, tool arguments or prompts. For each tool call it also sends the outcome and, on failure, an excerpt of the error text with e-mails, addresses, tokens, numbers of 4+ digits and quoted text replaced by #; a value from your request can appear in it if the error text contains it. Disable this telemetry for A1 MCP servers with:
ASKADS_TELEMETRY=0Limits and background work
Merchant Center processing is asynchronous. A newly inserted, updated or deleted product input can take several minutes to appear in processed products. Product and promotion approval issues appear later, not as an immediate API error.
Market Insights is optional. Price competitiveness and suggested-price reports return data only after the account opts into the free Market Insights program.
Quotas depend on the account and API method. Check current consumption with
list_method_quotas; Google’s daily counters reset at 12:00 UTC.Temporary limits are handled cautiously. When Google returns
429, the server followsRetry-Afterwhen provided and makes a limited number of retries. It does not replay a write after an uncertain network or server failure.There is no background monitoring. The server works only while an AI app calls it. If your AI app supports scheduled tasks, you can ask it to check product issues or quota use periodically.
Aggregated product issues have an account limitation.
list_product_issuesworks for standalone and sub-accounts, not advanced parent accounts.
Technical documentation
MCP capability catalog — task-oriented pages for every tool.
Support
Found a bug or need a scenario? Create an issue or write in Telegram.
Available Tools
28 toolsauth_statusGoogle connection statusARead-onlyIdempotent
Shows whether this server is connected to Google: token presence and source (env variables or a stored in-chat login), expiry, the Google account email, granted vs missing OAuth scopes, where the credentials file lives and where the OAuth client comes from. Makes no network calls and never returns the token itself. Call it first when other tools report the server is not connected.
Inputs: no named parameters.
create_data_sourceCreate an API data sourceA
Creates an API (generic) data source — the target that insert_product_input / update_product_input / insert_promotion need as data_source. Only API sources can be created through the API (file, UI and autofeed sources are set up in Merchant Center). For product sources content_language and feed_label must be both set or both omitted; countries applies to primary sources only. A promotions source requires target_country and content_language. Returns the created DataSource with its dataSourceId.
Inputs: type (required), display_name (required), account, countries, +3 more.
delete_product_inputDelete a product inputADestructive
Deletes a product input from a specific data source (data_source is required — the same product can exist in several sources, and only the targeted input is removed). product_input is "contentLanguagefeedLabelofferId" or the base64url name. Returns an empty object on success; the processed product disappears after async processing (minutes).
Inputs: data_source (required), product_input (required), account.
fetch_data_sourceRe-fetch a file feed nowA
Triggers an immediate re-fetch (re-read) of a file-based feed outside its regular schedule. Works only for data sources with a file input and fetch settings (scheduled fetch or Google Sheets); calling it on an API-type source is an error. Returns an empty object on success — the fetch itself runs asynchronously on Google's side.
Inputs: data_source (required), account.
finish_loginFinish the Google loginAIdempotent
Second step: waits up to 20 s for the browser consent to finish, saves the tokens to an owner-only file and verifies the login with a read-only identity call, returning the account email and the granted scopes. After success every tool works immediately — no client restart. If the user granted only part of the requested permissions, the login is still saved and missingScopes lists what will not work. Logging in under a different Google account replaces the previous login (its refresh token is revoked best-effort) and the response carries previousAccountEmail so the change never goes unnoticed.
Inputs: no named parameters.
get_accountGet a Merchant Center accountARead-onlyIdempotent
Returns a single Merchant Center account: name (accounts/{id}), accountId, accountName, languageCode, timeZone, adultContent and testAccount. Useful to verify the configured account or inspect a sub-account.
Inputs: account.
get_data_sourceGet a data sourceARead-onlyIdempotent
Returns one data source by its numeric ID (or full resource name): type, input (API/FILE/UI/AUTOFEED), feed configuration and fetch settings. Check input before calling fetch_data_source — only file-based feeds with fetch settings can be re-fetched.
Inputs: data_source (required), account.
get_homepageGet the store homepageARead-onlyIdempotent
Returns the store homepage of an account: uri and claimed (whether the homepage is verified and claimed by the merchant — a prerequisite for serving offers). An unclaimed homepage is a common reason for account-level problems; claiming/unclaiming is not exposed as a tool (use raw_request POST accounts/v1/accounts/{a}/homepage:claim if you really need it).
Inputs: account.
get_productGet a processed productARead-onlyIdempotent
Returns one processed product including productStatus.itemLevelIssues (code, severity, resolution, description) — the place to see why a product is disapproved. Identify the product either with product ("contentLanguagefeedLabelofferId", e.g. "enUSsku123", or the base64url base64EncodedName; legacy local products use a local~ prefix) or with the three components content_language + feed_label + offer_id. A product inserted moments ago may 404 until async processing finishes (minutes).
Inputs: account, product, offer_id, feed_label, +1 more.
get_promotionGet a promotionARead-onlyIdempotent
Returns one promotion including promotionStatus (per-destination approval and itemLevelIssues) — the place to check whether a freshly inserted promotion was approved.
Inputs: promotion (required), account.
get_shipping_settingsGet shipping settingsARead-onlyIdempotent
Returns the account-level shipping settings: services[] (delivery countries, delivery times, rate tables and carrier rates), warehouses[] and an etag. Read-only by design: the API's only write is shippingSettings:insert, a FULL REPLACE of every service — too dangerous for a tool; use raw_request if you really need it.
Inputs: account.
insert_product_inputInsert or replace a productADestructive
Uploads (upserts) a product into an API data source: an existing input with the same contentLanguagefeedLabelofferId in that data source is fully replaced. Requires data_source (an API-type source — create one with create_data_source or in Merchant Center; file feeds cannot be written). Inserting with a different data source MOVES the product to it. Returns the ProductInput (name, product = the future processed name, base64EncodedProduct). Processing is async: the processed product shows up in get_product/list_products after several minutes, and data-quality problems surface later in productStatus.itemLevelIssues, not as API errors. Prices go in product_attributes as {"price": {"amountMicros": "9990000", "currencyCode": "USD"}} (1 unit = 1,000,000 micros).
Inputs: offer_id (required), feed_label (required), data_source (required), content_language (required), +4 more.
insert_promotionInsert or update a promotionA
Creates or updates a promotion. Unlike product writes, the data source travels in the request BODY (the server assembles it). The promotion object requires promotionId, contentLanguage (ISO 639-1), targetCountry (CLDR, e.g. "US") and redemptionChannel (array with ONLINE and/or IN_STORE — at least one). Optional attributes carry longTitle, couponValueType, offerType, genericRedemptionCode, promotionEffectiveTimePeriod {startTime, endTime}, productApplicability, moneyOffAmount, percentOff, etc. Returns the Promotion incl. promotionStatus; approval happens asynchronously (check get_promotion later).
Inputs: promotion (required), data_source (required), account.
list_accountsList Merchant Center accountsARead-onlyIdempotent
Lists the Merchant Center accounts the authenticated user can access. Returns accounts[] (name, accountId, accountName, languageCode, timeZone, adultContent, testAccount) and nextPageToken. Use it first to discover the account ID the other tools need (or set GOOGLE_MERCHANTS_ACCOUNT_ID once). Optional filter uses the account filter syntax, e.g. accountName = "store".
Inputs: filter, page_size, page_token.
list_data_sourcesList data sourcesARead-onlyIdempotent
Lists the data sources of an account. Each has name (accounts/{a}/dataSources/{id}), dataSourceId, displayName, input (API | FILE | UI | AUTOFEED), exactly one type object (primaryProductDataSource, supplementalProductDataSource, promotionDataSource, ...) and fileInput for file feeds. Use it to find the API-type data source that insert_product_input / insert_promotion require as data_source.
Inputs: account, page_size, page_token.
list_method_quotasAPI quota usageARead-onlyIdempotent
Shows the account's Merchant API usage vs limits per method group (quota sub-API): quotaGroups[] with name, quotaUsage, quotaLimit (per day), quotaMinuteLimit and methodDetails[] listing the methods in each group. Daily counters reset at 12:00 UTC — midday, not midnight. Use it to diagnose HTTP 429 RESOURCE_EXHAUSTED errors and to see how much headroom is left.
Inputs: account, page_size, page_token.
list_product_issuesAggregated product issuesARead-onlyIdempotent
Lists aggregate product statuses per reporting context and country (issueresolution sub-API): stats {active, pending, disapproved, expiring counts} plus itemLevelIssues[] with how many products each issue affects — the fastest way to see what is wrong with a feed at a glance. Works only for sub-accounts and standalone accounts, NOT for advanced (parent) accounts. The filter supports only reporting_context and country, e.g. reporting_context = "SHOPPING_ADS" AND country = "US". For a single product's issues use get_product (productStatus.itemLevelIssues).
Inputs: filter, account, page_size, page_token.
list_productsList processed productsARead-onlyIdempotent
Lists the processed products of an account, as shown in Merchant Center. Each product has name (accounts/{a}/products/{contentLanguagefeedLabelofferId} — NO channel segment in v1), offerId, contentLanguage, feedLabel, dataSource, productAttributes (title, price, availability, ...), productStatus with itemLevelIssues, and base64EncodedName (use it when offerId contains URL-hostile characters like '/'). The list has no server-side filter — filter via search_reports on product_view. Recently inserted products appear only after async processing (minutes).
Inputs: account, page_size, page_token.
list_promotionsList promotionsARead-onlyIdempotent
Lists the promotions of an account: promotions[] (name, promotionId, contentLanguage, targetCountry, redemptionChannel, attributes, promotionStatus with destination statuses and itemLevelIssues) and nextPageToken.
Inputs: account, page_size, page_token.
logoutDisconnect from GoogleADestructive
Revokes the stored token at Google (oauth2.googleapis.com/revoke) and deletes the local credentials file. Tokens supplied via env variables are NOT touched — remove them from the MCP client config manually; envTokenStillSet in the response says whether any are still in effect.
Inputs: no named parameters.
price_competitivenessPrice competitiveness vs the marketARead-onlyIdempotent
Convenience wrapper over a canned MCQL query on price_competitiveness_product_view: for each product, your price vs the market benchmark_price (aggregated from comparable offers across merchants) with report_country_code. A product priced above the benchmark is losing clicks to cheaper rivals. Requires the account to be opted into Market Insights (free, in Merchant Center settings) — otherwise rows are empty. Price amounts are micros (1,000,000 = 1 unit) and may arrive as strings (int64). Optional country narrows to one report country.
Inputs: account, country, page_size, page_token.
price_insightsSuggested prices & predicted impactARead-onlyIdempotent
Convenience wrapper over a canned MCQL query on price_insights_product_view: Google's suggested_price per product with the predicted change in impressions, clicks and conversions if you adopt it (predicted_*_change_fraction, e.g. 0.05 = +5%), plus an overall effectiveness bucket (LOW/MEDIUM/HIGH). Requires the Market Insights opt-in — otherwise rows are empty. Price amounts are micros and may arrive as strings (int64).
Inputs: account, page_size, page_token.
raw_requestRaw Merchant API callADestructive
Escape hatch to call any Merchant API v1 path directly, for endpoints without a dedicated tool (e.g. "accounts/v1/accounts/123/issues" or the one-time "accounts/v1/accounts/123/developerRegistration:registerGcp"). The path must include the sub-API prefix (accounts/v1, products/v1, datasources/v1, promotions/v1, reports/v1, issueresolution/v1, quota/v1, inventories/v1, ...). query adds URL query parameters (e.g. dataSource for productInputs writes, updateMask for PATCH); body is sent as JSON. Can create, modify and delete data — use the dedicated tools when one exists.
Inputs: path (required), body, query, method.
search_reportsRun an MCQL report queryARead-onlyIdempotent
Runs a Merchant Center Query Language (MCQL) query via reports:search. Tables: product_view, product_performance_view, price_competitiveness_product_view, price_insights_product_view, non_product_performance_view, best_sellers_product_cluster_view, best_sellers_brand_view, competitive_visibility_top_merchant_view, competitive_visibility_competitor_view, competitive_visibility_benchmark_view. Rules: field names are snake_case in the query but camelCase in the JSON response; no SELECT ; performance views require a WHERE date range, e.g. SELECT offer_id, clicks, impressions FROM product_performance_view WHERE date BETWEEN '2026-07-01' AND '2026-07-31' ORDER BY clicks DESC. price_ views require the Market Insights opt-in. Each result row has exactly one populated view object. This is also the way to FILTER products (product_view) — list_products has no filter.
Inputs: query (required), account, page_size, page_token.
set_clientSave the OAuth clientAIdempotent
Saves the OAuth client credentials from the JSON file downloaded from Google Cloud Console ('Download JSON' on a Desktop-app client). Pass the file PATH — the secret must never be pasted into the chat. The client is stored once in the shared ~/.config/mcp-google-auth/client.json (owner-only) and reused by every mcp-google-* server; tokens stay per-server. After this, call start_login.
Inputs: path (required).
setup_instructionsSetup instructionsARead-onlyIdempotent
Step-by-step checklist for connecting this server to Google: creating a Google Cloud project and a Desktop-app OAuth client, publishing the consent screen (mandatory — Testing-mode refresh tokens die after 7 days), downloading the client JSON and handing its PATH to set_client. Works without any credentials; the checklist shortens to 'enable the API + log in' when an OAuth client is already configured (one client serves the whole mcp-google-* line). Never asks the user to paste secrets into the chat.
Inputs: no named parameters.
start_loginStart the Google loginAIdempotent
First step of connecting from the chat, without editing config files or restarting the client. Returns authorizeUrl — show it to the user as a clickable link and ask them to open it in the browser ON THIS MACHINE, pick the Google account and approve access. A one-shot listener on 127.0.0.1 catches Google's redirect; the code is exchanged locally and never passes through the chat. Does not open the browser itself. The attempt lives 10 minutes; when the browser shows the success page, call finish_login.
Inputs: no named parameters.
update_product_inputUpdate a product inputA
Sparse-updates an existing product input — the cheap way to change price or availability without re-sending the whole product. data_source must be the source holding the input. update_mask is a comma-separated list of attribute paths (e.g. "productAttributes.price,productAttributes.availability"); when omitted, all populated fields of the request are applied. Every path listed in update_mask MUST carry a value in this request — a masked path with no value ERASES that attribute (the tool rejects such requests locally; to clear an attribute intentionally use raw_request). Returns the updated ProductInput; the processed product refreshes after async processing (minutes). To create a product or replace it wholesale use insert_product_input.
Inputs: data_source (required), product_input (required), account, update_mask, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 28 tools
Almost every tool targets a distinct resource+action (accounts, products, product inputs, data sources, promotions, reports, auth flow), and descriptions explicitly cross-reference alternatives. The main soft spots are search_reports vs. the price_competitiveness/price_insights wrappers and vs. list_products filtering, which overlap in purpose though the docs explain when to use which. Auth helpers (start_login/finish_login/auth_status/setup_instructions) are a sequence, not duplicates, so they stay distinguishishable.
Uniform snake_case throughout with a predictable verb_noun shape (list_accounts, get_product, insert_product_input, delete_product_input, create_data_source). A handful of tools drop the verb (auth_status, setup_instructions, price_competitiveness, price_insights, raw_request, logout), but they are still readable and stylistically consistent rather than chaotic.
28 tools is on the heavy side of the rubric, driven largely by the six-step OAuth/onboarding flow plus a wide Google Merchant API surface. Each tool maps to a real API operation or documented convenience, so little feels padded, but the set is broader than an agent can comfortably hold in mind at once and could be consolidated (e.g. one auth tool, fewer report wrappers).
Covers the core lifecycle: account discovery, product-input CRUD, data-source create/list/fetch, promotion upsert/list/get, reporting, quotas and auth. Gaps are mostly deliberate (homepage claim and shipping-settings writes are read-only by design, no delete_data_source or promotion delete) and are explicitly routed to raw_request, so agents have a workaround. Inventory and returns sub-APIs are only reachable via the escape hatch.
Maintenance
Related MCP Connectors
E-commerce skills for AI agents: feeds, Google Shopping, GA4. Your private Brain when signed in.
Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.
SEO & marketing toolkit for AI agents: GA4, Search Console, AdSense, GTM, PageSpeed, Trends.
Google Ads MCP server: run Search, Display, Demand Gen and PMax campaigns from AI.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to manage Google Ads accounts by providing tools for querying account data and performing write operations such as updating campaign budgets, statuses, and bidding strategies.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server for Google Merchant Center, providing 126 tools to manage Google Shopping feed, products, inventory, reports, promotions, returns, and account configuration via natural language.813 PyPI19MIT
- AlicenseAqualityDmaintenanceEnables reading products, checking approval statuses, and analyzing feeds across multiple Google Merchant Center accounts via natural language.618 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Google Merchant Center through 34 tools across 9 modules, including account management, product operations, reports, inventory, promotions, shipping, return policies, collections, and recommendations.-