Withdraw an offer for an inventory item group (variation listing) to remove it from sale. Uses eBay's sell.inventory OAuth scope.
Withdraw an offer for an inventory item group (variation listing).
Required OAuth Scope: sell.inventory Minimum Scope: https://api.ebay.com/oauth/api_scope/sell.inventory
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Generated WithdrawByInventoryItemGroup body |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / bodyAdded value: +{
+ "description": "Generated WithdrawByInventoryItemGroup body"
+}Input schema / properties / requestRemoved value: -{
- "additionalProperties": true,
- "description": "Withdraw request with inventory item group key and marketplace ID",
- "properties": {
- "inventoryItemGroupKey": {
- "type": "string"
- },
- "marketplaceId": {
- "enum": [
- "EBAY_AT",
- "EBAY_AU",
- "EBAY_BE",
- "EBAY_CA",
- "EBAY_CH",
- "EBAY_CN",
- "EBAY_CZ",
- "EBAY_DE",
- "EBAY_DK",
- "EBAY_ES",
- "EBAY_FI",
- "EBAY_FR",
- "EBAY_GB",
- "EBAY_GR",
- "EBAY_HK",
- "EBAY_HU",
- "EBAY_ID",
- "EBAY_IE",
- "EBAY_IL",
- "EBAY_IN",
- "EBAY_IT",
- "EBAY_JP",
- "EBAY_MY",
- "EBAY_NL",
- "EBAY_NO",
- "EBAY_NZ",
- "EBAY_PE",
- "EBAY_PH",
- "EBAY_PL",
- "EBAY_PR",
- "EBAY_PT",
- "EBAY_RU",
- "EBAY_SE",
- "EBAY_SG",
- "EBAY_TH",
- "EBAY_TW",
- "EBAY_US",
- "EBAY_VN",
- "EBAY_ZA",
- "EBAY_HALF_US",
- "EBAY_MOTORS_US"
- ],
- "type": "string"
- }
- },
- "required": [
- "inventoryItemGroupKey",
- "marketplaceId"
- ],
- "type": "object"
-}Input schema / requiredPrevious value: -[
- "request"
-]New value: +[
+ "body"
+]v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only states action and required OAuth scope. It does not disclose side effects, reversibility, or any behavioral traits beyond the basic mutation.
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?
Two sentences: first states purpose, second lists required scope. Very concise and front-loaded, though scope could be integrated into the first sentence.
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?
With one parameter and no output schema, description covers purpose and scope. But it omits prerequisites, return values, and any state dependencies, leaving gaps for a mutation tool.
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 coverage is 100% with one parameter 'body', but its description 'Generated WithdrawByInventoryItemGroup body' is vague. The tool description adds no extra meaning beyond the schema.
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?
The description clearly states the tool withdraws an offer for an inventory item group (variation listing), using specific verb and resource. It distinguishes from sibling ebay_withdraw_offer which is for single offers.
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?
The description implies usage for variation listings via 'inventory item group (variation listing)', providing clear context. However, it lacks explicit exclusions or when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.