Skip to main content
Glama
Sign In

Google Merchant Center MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Google Merchant Center Setup Helper

query_contexts
Read-only

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.

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": {
      "request": "<request>"
    },
    "name": "query_contexts"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionsNo
requestYes
brand_idNo
platformNo
workspace_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description aligns by describing only discovery/metadata retrieval. It adds valuable behavioral context beyond annotations: the required two-step sequence before querying and what information each step returns. It does not mention auth, rate limits, or pagination, but those gaps are less critical given the read-only annotation and output schema.

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?

The numbered steps are front-loaded and easy to follow, and the note that available_actions is already included in accounts prevents redundant calls. There is slight repetition in describing optional calls, but overall it is efficient.

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?

For a read-only, multi-mode discovery tool with an output schema and readOnlyHint annotation, the description covers the essential workflow, required sequencing, and most parameter meanings. The only notable omission is the platform parameter, which is left unexplained.

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?

Schema description coverage is 0%, so the description must compensate. It does well for request, actions, brand_id, and workspace_id by explaining their roles and conditional usage, but the platform parameter is never mentioned, leaving one of five parameters undocumented in both schema and description.

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

Purpose4/5

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

The description clearly frames this as a planning/discovery helper for Google Merchant Center queries, and it specifies what each request value retrieves (accounts metadata, action details, brand guidelines). It does not explicitly distinguish itself from the sibling query_data or execute_action, but the read-only metadata-retrieval purpose is still clear.

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?

The description gives an explicit required workflow: first call request='accounts', then request='actions_details' with actions from available_actions before querying. It also labels available_actions and brands as optional and notes that available_actions is already included in accounts, leaving no ambiguity about sequencing.

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