Skip to main content
Glama

ebay_revise_listing

Revise an existing eBay fixed-price listing by updating specific fields such as quantity, price, or title. Send only the fields 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
itemIdYesThe eBay item ID to revise
fieldsYesFields to update (e.g., { "Quantity": 10, "StartPrice": 14.99 })
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states it uses the Trading API (ReviseFixedPriceItem) and requires a User OAuth token, and explains the partial update strategy. However, it does not disclose whether the operation is destructive, if it can change listing format, or any rate limits, leaving some behavioral gaps.

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 very concise and well-structured: first sentence states purpose, second paragraph explains API and partial update strategy, third paragraph gives clear examples, and last sentence states the requirement. Every sentence adds value with no fluff.

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

Completeness4/5

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

Given no annotations or output schema, the description provides enough context for a revise tool: what it does, how to use it, and a requirement. It could mention listing state prerequisites (e.g., must be active) or error behavior, but overall it is sufficient for an agent to use the tool correctly.

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 has 100% description coverage, but the description adds significant value beyond the schema. It provides concrete examples (e.g., { 'Quantity': 10 }) and explains that only changed fields need to be sent, clarifying the usage of the 'fields' parameter beyond the schema's generic definition.

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', specifying it can update quantity, price, title, description, or any other field. This distinguishes it from sibling tools like ebay_create_listing or ebay_end_listing.

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

Usage Guidelines4/5

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

The description gives clear guidance: 'Only send the fields you want to change' and provides examples. It also mentions the required OAuth token. However, it does not explicitly state when not to use this tool or mention alternatives among siblings, though the context is reasonably clear.

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