Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_create_or_replace_inventory_location

Create or replace an eBay inventory location, including address, hours, and other details.

Instructions

Create or replace an inventory location

Input Schema

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

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

No annotations are present, and the description does not disclose any behavioral traits such as whether the operation is idempotent, what happens on conflict, or if it requires special permissions. This is a significant gap for a creation/replacement tool.

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

Conciseness2/5

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

The description is a single sentence, which is concise but under-specified. It does not earn its space by providing sufficient information for an agent to understand the tool's function.

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

Completeness1/5

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

Given the complexity of the nested 'location' object and the lack of annotations and output schema, the description is severely incomplete. It should explain key details like required subfields, behavior on replace, and the effect of missing fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is 100%, the descriptions are minimal ('The merchant location key', 'Location details') and add little value beyond the schema. The nested object properties within 'location' have no descriptions, so the tool description fails to clarify parameter semantics.

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 the verb 'create or replace' and the resource 'inventory location' clearly, but it does not differentiate from sibling tools like 'ebay_update_location_details' or 'ebay_delete_inventory_location'.

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 vs. alternatives like 'ebay_update_location_details' or 'ebay_delete_inventory_location' is provided. The description lacks any context for appropriate 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/jyarbro/ebay-seller-mcp'

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