Skip to main content
Glama

Publish a model's eBay variation listing

publish_ebay_variation_listing
Destructive

Publish a product model on eBay as ONE live listing with variations: saves it first exactly like save_ebay_variation_listing (so eBay gets the articles as they are now), then publishes the whole group — a real listing buyers can purchase. Returns status: blocked (with issues — reason, message, skus — and nothing written), saved (a draft on eBay) or published, plus marketplaceId, listingId, listingUrl, publishedAt, variationCount, failed (variations eBay refused, by sku — nothing is published while any) and removedSkus (articles that left the listing). A partial/uncertain publication returns reason ebayVariationReconciliationPending with retryable=true. Retry the same operation to check eBay first; never withdraw or delete to repair it. Confirmed recovery updates CRM links without publishing again. Needs listing creation armed on the eBay connection, and is refused until the workspace owner switches on AI publishing. Confirm with the user before calling. The result echoes the workspace.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model": "<model>"
    },
    "name": "publish_ebay_variation_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesThe product model: its code — the productGroupId get_product and search_products return for every article of it — or its id. Its active articles on the eBay channel become the listing's variations.
marketplaceIdNoeBay marketplace id (EBAY_IT, EBAY_DE…) for a FIRST save, when the connection sells on several. A saved listing keeps its marketplace; omit it then.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds substantial context: it first saves articles as-is then publishes, discloses the status outcomes (blocked/saved/published) and that nothing is written while any variation fails, and explains the reconciliation-pending retryable path. This is rich behavior beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the key save-then-publish behavior are front-loaded, and the status/return enumeration is informative rather than filler. It is dense and slightly run-on, but nearly every clause earns its place.

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

Completeness5/5

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

There is no output schema, so the description correctly explains the return shape (statuses plus marketplaceId, listingId, listingUrl, publishedAt, variationCount, failed, removedSkus) and the reconciliation case. For a complex destructive mutation tool it is complete enough for correct invocation.

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?

Schema description coverage is 100%, so both parameters (model, marketplaceId) are fully documented in the schema. The description does not add syntax or meaning beyond that, so the baseline 3 is appropriate.

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?

States a specific verb+resource+scope: publishes a product model on eBay as ONE live listing with variations, and explicitly ties it to save_ebay_variation_listing by saying it saves first. An agent can distinguish it from save_ebay_variation_listing, get_ebay_variation_listing, and withdraw_ebay_variation_listing without opening any schema.

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?

Gives explicit conditions and exclusions: confirm with the user before calling, needs listing creation armed on the eBay connection, refused until the workspace owner enables AI publishing; and 'never withdraw or delete to repair' a reconciliation-pending state. It also names the correct retry behavior, leaving little to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources