ebay_delete_inventory_location
Delete an inventory location from eBay by providing its merchant location key.
Instructions
Delete an inventory location
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| merchantLocationKey | Yes | The merchant location key |
Delete an inventory location from eBay by providing its merchant location key.
Delete an inventory location
| Name | Required | Description | Default |
|---|---|---|---|
| merchantLocationKey | Yes | The merchant location key |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavioral traits. It only says 'delete' without indicating whether it's a soft or hard delete, if it is irreversible, or any side effects like cascading to other entities.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that directly states the tool's purpose. No extraneous words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a deletion tool with no output schema, the description fails to explain return behavior, error conditions, or idempotency. The parameter description is tautological, providing no additional context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (one parameter fully described in schema), so baseline is 3. The description adds no new meaning; it just restates 'The merchant location key', which is redundant with the parameter name.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (delete) and the resource (inventory location). It distinguishes itself from sibling tools like create, get, or enable by using the verb 'delete'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like ebay_disable_inventory_location or ebay_get_inventory_location. No prerequisites or context for when deletion is appropriate are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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