Skip to main content
Glama

ebay_disable_inventory_location

Disable an eBay inventory location by providing its merchant location key, making it inactive for new listings.

Instructions

Disable an inventory location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
merchantLocationKeyYesThe merchant location key
Behavior1/5

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

The description does not disclose any behavioral traits beyond the action 'disable'. There is no information about side effects, whether the location can be re-enabled, or any other consequences. Given the absence of annotations, the description fails to provide necessary transparency.

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

Conciseness3/5

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

The description is extremely concise (one sentence, 4 words), but this brevity comes at the cost of missing necessary details. It is not appropriately structured for decision-making, as it lacks context about the operation's effects.

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?

The tool has low complexity (1 parameter, no output schema, no nested objects), but the description still feels incomplete. It does not explain what happens after disabling (e.g., confirmation or error handling). More context is needed for an agent to use it correctly.

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 parameter 'merchantLocationKey' is fully documented in the schema, and the description adds no additional meaning. According to the guidelines, when schema coverage is 100%, the baseline score is 3.

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 verb 'disable' and the resource 'inventory location', making the purpose understandable. However, it does not explicitly differentiate from similar tools like ebay_delete_inventory_location or ebay_enable_inventory_location, lacking a clear distinction.

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 is provided on when to use this tool versus alternatives, such as specifying that disabling is reversible while deleting is not. The description offers no usage context or prerequisites.

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/YosefHayim/ebay-mcp'

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