Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_revise_listing

Revise an existing fixed-price eBay listing by updating quantity, price, title, or other fields. Send only the fields you want to change.

Instructions

Revise an existing fixed-price listing. Update quantity, price, title, description, or any other field.

Uses the Trading API (ReviseFixedPriceItem). Only send the fields you want to change.

Examples:

  • Update quantity: { "Quantity": 10 }

  • Update price: { "StartPrice": 14.99 }

  • Update title: { "Title": "New Title" }

  • Multiple fields: { "Quantity": 10, "StartPrice": 14.99 }

Required: User OAuth token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesFields to update (e.g., { "Quantity": 10, "StartPrice": 14.99 })
itemIdYesThe eBay item ID to revise
Behavior3/5

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

The description mentions the underlying API (ReviseFixedPriceItem) and the requirement of a User OAuth token, which are important behavioral traits. However, without annotations, the description fails to disclose mutation behavior such as side effects, rate limits, or what the response contains. It provides basic transparency but lacks depth.

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 concise with no wasted words. It front-loads the purpose, includes a useful usage tip, and provides clear examples. Every sentence adds value.

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?

Given the lack of annotations and output schema, the description covers the essential aspects: purpose, authentication, and partial update pattern. However, it omits details about return values, error handling, and the scope (only fixed-price listings), making it moderately complete for the tool's complexity.

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

Parameters4/5

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

The input schema already describes both parameters with 100% coverage, so the baseline is 3. The description adds value by providing concrete examples (e.g., 'Update quantity: { "Quantity": 10 }'), which clarify the structure of the 'fields' parameter beyond the schema's generic description.

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 the verb 'revise' and the resource 'existing fixed-price listing', making the tool's purpose unambiguous. It distinguishes itself from sibling tools like create, end, or relist by specifying that it modifies an existing fixed-price listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description advises to 'Only send the fields you want to change', which is helpful for partial updates. However, it does not provide guidance on when to prefer this tool over alternatives (e.g., ebay_create_listing for new listings, ebay_end_listing to end, ebay_bulk_update_price_quantity for batch updates) or when not to use it (e.g., auction listings).

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