Hosted Google Merchant Center MCP server, with each action switched on or off per account.
Scored across 4 tools
query_contexts and prompts_menu are reasonably distinct, but query_data and execute_action have nearly identical descriptions and both present themselves as the same final workflow step. An agent must rely mainly on the verbs 'query' vs 'execute' to distinguish them, which is workable but not crisp.
Three tools follow a clear verb_noun pattern: execute_action, query_contexts, query_data. prompts_menu deviates by using a noun_noun form, but the overall convention is still readable and predictable.
Four tools is a reasonable, compact set for a workflow-oriented Merchant Center server. Each tool has a role: context discovery, data querying, action execution, and prompt browsing.
The generic query_data and execute_action tools, backed by query_contexts for schema/action discovery, appear to cover both reading data and performing Merchant Center actions. Minor gaps may exist around explicit lifecycle helpers, but the surface is broad enough for the stated purpose.
Execute Google Merchant Center action (Step 3 (FINAL) of workflow).
REQUIRED: Complete these steps first using query_contexts:
request='accounts' - Get workspace_id, brand_id AND available_actions
request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions
IMPORTANT: Always call step 2 to see the exact body structure before executing.
Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.
Inputs: body (required). Returns: object
Helper for planning InsightfulPipe Google Merchant Center data queries.
Step 1: request='accounts' – Retrieve workspace_id, brand_id, other source metadata, AND available_actions (all tables you can query).
Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.
Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).
Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.
Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object
Query Google Merchant Center data (Step 3 (FINAL) of workflow).
REQUIRED: Complete these steps first using query_contexts:
request='accounts' - Get workspace_id, brand_id AND available_actions
request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions
IMPORTANT: Always call step 2 to see the exact body structure before querying.
Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.
Inputs: body (required). Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Hosted Google Business Profile MCP server, with each action switched on or off per account.
Hosted Google Search Console MCP server, with each action switched on or off per account.
Hosted Google Tag Manager MCP server, with each action switched on or off per account.
Hosted Google Analytics 4 MCP server, with each action switched on or off per account.
Add one secure layer between your agents and this server.
