Skip to main content
Glama
Sign In

Google Merchant Center MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Google Merchant Center Execute Action

execute_action
Destructive

Execute Google Merchant Center action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "execute_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the agent knows this mutates external state. The description is consistent with those flags and adds the prerequisite workflow, but it does not describe what the action actually does or what is affected—so it adds process context, not side-effect detail beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the numbered required steps, which are efficient for a workflow tool. There is minor redundancy between the step 2 text and the subsequent 'Always call step 2' reminder, but overall it is well organized and each element is actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the destructive/openWorld profile is covered by annotations. For a complex, free-form-body execution step, the description supplies the full prerequisite path to build the body—leaving only the specific effect of each action unstated, which is deferred to query_contexts by design.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single body parameter has 0% schema coverage and is a free-form nested object. The description compensates by telling the agent to source the exact body structure from query_contexts request='actions_details' and 'follow the schema exactly'—useful routing, but it never explains the internal shape of body itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb (Execute) and resource (Google Merchant Center action) and situates it as the FINAL step of a workflow, which distinguishes it from query_contexts. However, 'action' is left undefined—an agent cannot tell what kinds of actions exist or what execution does without first calling query_contexts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (Step 3, final) and the mandatory prerequisite sequence, naming the sibling query_contexts and the exact request values ('accounts', 'actions_details'). It goes further to say 'Always call step 2' before executing, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Google Merchant Center MCP by InsightfulPipe toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources