Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_listing_set

Retrieve a set of listings for a promotion using eBay Marketing API. Specify promotionId and optional filters to view the exact listing set.

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.5/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only states 'Get listing set through the eBay Marketing API', which reveals nothing about read-only nature, required permissions, side effects, or other behavioral traits.

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

Conciseness3/5

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

The description is extremely concise (one sentence), but lacks substance. It could benefit from a brief explanation of what a listing set is without being verbose.

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?

Given no output schema and 6 parameters, the description is incomplete. It does not explain the return value, how it relates to other tools like 'ebay_get_promotions', or any operational context like pagination.

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 coverage is 100%, so baseline is 3. However, parameter descriptions are generic ('q optional endpoint parameter') and the tool description adds no additional meaning beyond what the schema already provides.

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 the verb 'Get' and resource 'listing set', so purpose is somewhat clear. However, it does not differentiate from siblings like 'ebay_get_listing' or 'ebay_get_promotions', and the term 'listing set' is not explained, leaving ambiguity.

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?

No guidance on when to use this tool over alternatives. The description does not mention the context of promotions or provide any criteria for selecting this tool among many similar 'get' tools.

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