Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_get_listing_violations

Fetches eBay listing compliance violations. This tool is retired and always fails; use eBay Seller Hub's Issue Resolution Center instead.

Instructions

DECOMMISSIONED: eBay shut down the Sell Compliance API on 2026-03-30. This tool always fails with a clear message. Use Seller Hub → Performance → Issue Resolution Center instead (no API equivalent).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
filterNo
offsetNo
complianceTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.14.1
    • removedInput schema / properties / complianceType / description
      Removed value: -"Type of compliance violation"
    • addedInput schema / properties / filter
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / limit / description
      Removed value: -"Number of violations to return"
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • removedInput schema / properties / offset / description
      Removed value: -"Number of violations to skip"
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
  2. First observedv1.8.10

TDQS

A5/5.0
Behavior5/5

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

Despite no annotations, the description fully discloses the tool's behavior: it always fails due to API shutdown. No hidden surprises.

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

Conciseness5/5

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

Extremely concise, front-loaded with 'DECOMMISSIONED', and every sentence provides critical information. No wasted words.

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?

For a decommissioned tool, the description is fully complete: it states the failure, reason, and alternative. Nothing more is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Parameters are irrelevant since the tool is dead. The description sensibly avoids misleading parameter explanations, implying their irrelevance.

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?

The description clearly states the tool is decommissioned and always fails, with explicit reason and alternative. The purpose is unambiguously communicated: this tool is non-functional.

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?

The description explicitly warns not to use the tool and provides a concrete alternative (Seller Hub). This is perfect usage guidance for a decommissioned tool.

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