Skip to main content
Glama

ebay_create_or_replace_inventory_location

Create or update an inventory location on eBay with address, hours, and contact info. Use this to manage your eBay store or warehouse locations.

Instructions

Create or replace an inventory location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
merchantLocationKeyYesThe merchant location key
locationYesLocation details
Behavior2/5

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

With no annotations provided, the description must convey behavior. It states 'create or replace' implying mutation, but does not disclose side effects (e.g., overwriting existing data, impact on associated entities) or required permissions. This is insufficient for a potentially destructive operation.

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 (4 words) but lacks structure. While no extra verbiage, it does not include essential context like purpose or usage scope, making it under-specified.

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?

Given the tool's complexity (nested objects, 2 required params) and no output schema, the description is incomplete. It does not explain what an inventory location is, that it can replace an existing one, or how it differs from 'ebay_update_location_details'. More detail is needed for correct use.

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 100%, so parameters are already documented. The description adds no further meaning about parameter usage or constraints (e.g., format of merchantLocationKey, allowed location types). At baseline level.

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 'Create or replace an inventory location' clearly states the action (create or replace) and the resource (inventory location). However, it does not distinguish this tool from sibling tools like 'ebay_update_location_details' or 'ebay_create_inventory_item', leaving ambiguity about when to use which.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, when to choose create vs replace, or comparison with related tools like 'ebay_update_location_details'.

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