Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_listing_set

Read-only

Fetch listing sets for a promotion through the eBay Marketing API. Supply a promotionId to retrieve associated listings with optional filters for sorting, status, and pagination.

Instructions

Get listing set through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoq optional endpoint parameter
sortNosort optional endpoint parameter
limitNolimit optional endpoint parameter
offsetNooffset optional endpoint parameter
statusNostatus optional endpoint parameter
promotionIdYespromotionId required endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.14.1
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "limit optional endpoint parameter",
+  "type": "number"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "offset optional endpoint parameter",
+  "type": "number"
+}
    • changedInput schema / properties / promotionId / description
      Previous value: -"Promotion ID"New value: +"promotionId required endpoint parameter"
    • addedInput schema / properties / q
      Added value: +{
+  "description": "q optional endpoint parameter",
+  "type": "string"
+}
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "sort optional endpoint parameter",
+  "type": "string"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "status optional endpoint parameter",
+  "type": "string"
+}
  2. First observedv1.8.10

TDQS

C2.6/5.0
Behavior2/5

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

The annotation readOnlyHint=true already informs the agent this is a read-only operation. The description adds no further behavioral context: it does not mention pagination (despite limit/offset parameters), response format, or that the listing set is tied to a promotion. With annotations covering safety, the bar is lower, but the description still fails to disclose what the operation returns or any constraints beyond the schema.

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?

The description is a single concise sentence with no wasted words, and the key action is front-loaded. It is appropriately sized for such a simple statement, though the content is vague. The structure is clean and efficient.

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

Completeness2/5

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

The tool has no output schema, so the description should explain what a 'listing set' is and what the response contains, but it does not. Given the large sibling context and the need to distinguish this tool from many similar ones, the description is inadequate for an agent to invoke it correctly without additional external knowledge.

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 the baseline is 3. However, the schema descriptions are minimal ('q optional endpoint parameter'), and the tool description adds no explanation of what 'q', 'sort', 'status', or other parameters mean in this context. The description does not compensate for the lack of semantic detail, but since the schema covers every parameter, a 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ('Get listing set') and identifies the API ('eBay Marketing API'), but it does not explain what a 'listing set' is or how it differs from sibling tools like ebay_get_promotions, ebay_get_listing, or ebay_get_promotion_reports. The purpose is vague because the key term is undefined and no distinguishing context is given.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It merely states the action and API without any context, prerequisites, or exclusions, leaving the agent to infer usage from the tool name and parameters.

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