mcp-google-merchant-center
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MERCHANT_ID | Yes | Default Merchant Center account ID | |
| GOOGLE_APPLICATION_CREDENTIALS | Yes | Path to ADC credentials JSON file |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountB | Recupera informazioni sull'account Merchant Center |
| list_productsC | Lista prodotti nel Merchant Center |
| get_productC | Recupera dettagli di un prodotto specifico |
| search_productsC | Cerca prodotti per titolo o brand |
| list_data_sourcesB | Lista feed e fonti dati del Merchant Center |
| get_product_statusC | Stato di approvazione e issues dei prodotti |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a clear, distinct aspect: account info, product details, product status, data sources, product listing, and product search. There is minimal overlap, as get_product and get_product_status differ in focus (details vs. approval), and list_products vs. search_products differ in scope (all vs. filtered).
All tools follow a consistent verb_noun pattern using snake_case (e.g., get_account, list_data_sources). The verbs (get, list, search) clearly indicate the action, making the naming predictable and easy to understand.
With 6 tools, the server is well-scoped for querying a Google Merchant Center. The number is neither too few (covering essential read operations) nor too many (no unnecessary clutter). It fits the apparent purpose of data retrieval.
The tool set covers key read operations: account, product details, product status, data sources, and product listing/search. However, it lacks write operations (e.g., create, update, delete). This may be intentional for a query-only server, but for full lifecycle management, it's slightly incomplete.