Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_offers

Retrieve offers for a specific seller-defined SKU. Filter by marketplace, listing format, and paginate to manage results.

Instructions

Get offers for one seller-defined SKU. To enumerate offers across SKUs, call ebay_get_inventory_items first, then call this tool once per SKU.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuYesSeller-defined SKU whose offers to return
limitNoNumber of offers to return
formatNoFilter offers by listing format
offsetNoNumber of offers to skip
marketplaceIdNoFilter offers by marketplace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.16.0
    • changedInput schema / properties / format / description
      Previous value: -"Filter by listing format"New value: +"Filter offers by listing format"
    • changedInput schema / properties / marketplaceId / description
      Previous value: -"Filter by marketplace ID"New value: +"Filter offers by marketplace"
    • changedInput schema / properties / sku / description
      Previous value: -"Filter by SKU"New value: +"Seller-defined SKU whose offers to return"
    • addedInput schema / properties / sku / minLength
      Added value: +1
    • addedInput schema / required
      Added value: +[
+  "sku"
+]
  2. Changed2 schema fields changedv1.14.1
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Filter by listing format",
+  "type": "string"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Number of offers to skip",
+  "type": "number"
+}
  3. First observedv1.8.10

TDQS

A4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It does not disclose any behavioral traits such as pagination behavior, response format, authentication requirements, or error conditions. For a read operation, this is a significant gap.

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?

Two concise sentences, front-loaded with the primary purpose, followed by a usage hint. No wasted words, and the structure is efficient.

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?

For a simple read tool with 5 parameters and no output schema, the description provides the essential workflow and clarifies the single-SKU scope. It does not mention pagination details, but the schema includes limit/offset, so that is partially covered. Overall, fairly complete for its simplicity.

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?

The input schema covers all parameters with descriptions (100% coverage), so the description adds no additional parameter meaning. The baseline of 3 is appropriate since the schema handles parameter semantics.

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 tool gets offers for one seller-defined SKU, using a specific verb and resource. It also differentiates from the workflow of enumerating across SKUs by referencing ebay_get_inventory_items, distinguishing it from sibling tools like ebay_get_offers_by_skus and ebay_get_offer.

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

Usage Guidelines5/5

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

Explicitly provides when to use this tool (for a single SKU) and when to use an alternative workflow (call ebay_get_inventory_items first, then this tool per SKU). This gives clear usage direction without ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools