Skip to main content
Glama
Sign In

Google Merchant Center MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Google Merchant Center Prompts

prompts_menu
Read-only

Browse the Google Merchant Center prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

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": "prompts_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
is_customNo
prompt_idNo
prompt_typeNo
workspace_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this as a safe read operation, and the description is consistent with that. It adds useful mode-specific context, including that 'menu' lists public/system prompts and that workspace prompts require is_custom plus workspace_id, but it does not cover pagination, auth, or other operational details.

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

Conciseness5/5

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

The description is short, front-loaded, and organized as two numbered request modes. Each sentence contributes directly to understanding how to invoke the tool, with no unnecessary prose.

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?

Given that an output schema exists, the description need not explain return values, and the readOnlyHint annotation covers safety. It explains the two modes and most parameter conditions adequately, though the semantics of prompt_type remain under-specified.

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 has to carry parameter meaning, and it does explain request, prompt_id, is_custom, and workspace_id usage. However, it only says prompt_type may optionally be passed without explaining what values it accepts or what it filters, leaving a clear gap for one of the five parameters.

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 states a specific verb and resource: browsing the Google Merchant Center prompt catalog, and it distinguishes the two request modes (menu listing vs. prompt_details fetching). It does not explicitly position itself against the sibling tools, so it is clear but lacks sibling differentiation.

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

Usage Guidelines4/5

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

The description clearly explains when to use each request value: 'menu' for listing prompts and 'prompt_details' for fetching a prompt body. It also says to set is_custom=True with workspace_id for workspace prompts, but it gives no when-not guidance or comparison to sibling tools.

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