Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_get_inventory_items

Retrieve a seller's complete list of inventory items from eBay, with optional pagination controls for limit and offset.

Instructions

Retrieve all inventory items for the seller.

Required OAuth Scope: sell.inventory.readonly or sell.inventory Minimum Scope: https://api.ebay.com/oauth/api_scope/sell.inventory.readonly

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of items to return (max 100)
offsetNoNumber of items to skip
Behavior3/5

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

The description adds OAuth scope requirements, which is useful behavioral information not in annotations (none provided). However, it does not mention pagination behavior, rate limits, or what happens if no items exist. The parameter descriptions for limit/offset are in the schema, not the description.

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?

The description is two sentences plus a scope line, all front-loaded with essential information. Every part earns its place without unnecessary verbosity.

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

Completeness3/5

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

For a tool with 2 fully described parameters, no output schema, and no annotations, the description is adequate but lacks details on return format and pagination behavior. It meets minimum viability but could be improved.

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% with both limit and offset having descriptions. The tool description does not add additional meaning beyond what the schema provides, 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Retrieve all inventory items for the seller', using a specific verb and resource. This distinguishes it from siblings like ebay_get_inventory_item (single item) and ebay_bulk_get_inventory_item (bulk retrieval).

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 such as ebay_get_inventory_item or ebay_bulk_get_inventory_item. The description does not provide context for selecting this tool among similar inventory retrieval options.

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