Skip to main content
Glama
gioenjoy

mcp-google-merchant-center

by gioenjoy

get_account

Retrieves detailed information about a Google Merchant Center account, such as account status and settings, using the account's merchant ID.

Instructions

Recupera informazioni sull'account Merchant Center

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
merchant_idNoMerchant Center ID (opzionale, default 123456789). Disponibili: 5291449515, 5747906518, 5443978365
Behavior3/5

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

Without annotations, the description implies a read operation ('recupera informazioni'), but it does not explicitly state that it is non-destructive or mention any side effects. Adequate but not comprehensive.

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?

A single sentence with no wasted words. It is front-loaded and concise.

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

Completeness2/5

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

No output schema is provided, and the description does not mention what information is returned (e.g., account name, settings). Also lacks details on potential errors or authentication requirements.

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 coverage is 100%, and the parameter description provides default and available IDs. The tool description does not add additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 states the tool retrieves Merchant Center account information, matching the tool name. It distinguishes from sibling tools like get_product and list_products, which focus on products.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description does not mention any prerequisites or context for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gioenjoy/mcp-google-merchant-center'

If you have feedback or need assistance with the MCP directory API, please join our Discord server