Create a new offer for an inventory item to list it on eBay. Provide the required offer details to start selling.
Create a new offer for an inventory item
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Generated EbayOfferDetailsWithKeys request body |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / bodyAdded value: +{
+ "description": "Generated EbayOfferDetailsWithKeys request body"
+}Input schema / properties / offerRemoved value: -{
- "additionalProperties": true,
- "description": "Offer details including SKU, marketplace, pricing, and policies",
- "properties": {
- "availableQuantity": {
- "type": "number"
- },
- "categoryId": {
- "type": "string"
- },
- "format": {
- "enum": [
- "AUCTION",
- "FIXED_PRICE"
- ],
- "type": "string"
- },
- "listingDescription": {
- "type": "string"
- },
- "listingPolicies": {
- "additionalProperties": true,
- "properties": {
- "bestOfferTerms": {
- "additionalProperties": true,
- "properties": {
- "autoAcceptPrice": {
- "additionalProperties": true,
- "properties": {
- "currency": {
- "type": "string"
- },
- "value": {
- "type": "string"
- }
- },
- "required": [
- "currency",
- "value"
- ],
- "type": "object"
- },
- "autoDeclinePrice": {
- "$ref": "#/properties/offer/properties/listingPolicies/properties/bestOfferTerms/properties/autoAcceptPrice"
- },
- "bestOfferEnabled": {
- "type": "boolean"
- }
- },
- "type": "object"
- },
- "eBayPlusIfEligible": {
- "type": "boolean"
- },
- "fulfillmentPolicyId": {
- "type": "string"
- },
- "paymentPolicyId": {
- "type": "string"
- },
- "returnPolicyId": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "marketplaceId": {
- "type": "string"
- },
- "merchantLocationKey": {
- "type": "string"
- },
- "pricingSummary": {
- "additionalProperties": true,
- "properties": {
- "minimumAdvertisedPrice": {
- "$ref": "#/properties/offer/properties/listingPolicies/properties/bestOfferTerms/properties/autoAcceptPrice"
- },
- "originalRetailPrice": {
- "$ref": "#/properties/offer/properties/listingPolicies/properties/bestOfferTerms/properties/autoAcceptPrice"
- },
- "price": {
- "$ref": "#/properties/offer/properties/listingPolicies/properties/bestOfferTerms/properties/autoAcceptPrice"
- },
- "pricingVisibility": {
- "enum": [
- "NONE",
- "PRE_CHECKOUT",
- "DURING_CHECKOUT"
- ],
- "type": "string"
- }
- },
- "required": [
- "price"
- ],
- "type": "object"
- },
- "quantityLimitPerBuyer": {
- "type": "number"
- },
- "sku": {
- "type": "string"
- },
- "tax": {
- "additionalProperties": true,
- "properties": {
- "applyTax": {
- "type": "boolean"
- },
- "thirdPartyTaxCategory": {
- "type": "string"
- },
- "vatPercentage": {
- "type": "number"
- }
- },
- "type": "object"
- }
- },
- "required": [
- "sku",
- "marketplaceId",
- "format"
- ],
- "type": "object"
-}Input schema / requiredPrevious value: -[
- "offer"
-]New value: +[
+ "body"
+]v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries full responsibility for behavioral disclosure. It fails to mention authentication needs, rate limits, side effects (e.g., creation triggers), or that it mutates state. Only a minimal verb is given.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence, which is concise but lacks necessary detail. It is not wasteful, but it could be more informative without sacrificing brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with one complex parameter and no output schema, the description is incomplete. It does not explain what an offer is, what the body should contain, or what a successful response looks like. This forces an agent to rely on external knowledge.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% but the description for the 'body' parameter is 'Generated EbayOfferDetailsWithKeys request body', which is vague. The main description adds no further details about required fields, format, or constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action ('Create') and the resource ('new offer for an inventory item'). However, it does not differentiate from the sibling tool 'ebay_bulk_create_offer' which creates multiple offers, leaving ambiguity about singular vs bulk.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like 'ebay_bulk_create_offer' or 'ebay_update_offer'. No prerequisites (e.g., inventory item must exist) or context for usage are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.