Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_bulk_delete_ads_by_inventory_reference

Delete multiple eBay CPS campaign ads at once by specifying inventory references (SKU or item group). Streamline bulk ad removal for efficient inventory management.

Instructions

Delete multiple ads by inventory reference. CPS campaigns only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adsYesBulk ad deletion request
campaignIdYesCampaign ID
Behavior2/5

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

No annotations are provided, so the description must carry behavioral context. It only states the action, missing details on idempotency, error handling, bulk limits, or post-deletion state. For a destructive bulk operation, this is insufficient.

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?

The description is extremely concise with two sentences, no redundancy, and front-loads the action. Every word adds value.

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?

With no output schema and missing annotations, the description should explain return values, error scenarios, or success indicators. It lacks this context, making it incomplete for a bulk mutation tool.

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% with descriptions for both parameters. The tool description does not add parameter-specific guidance beyond what the schema provides. 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?

The description clearly states the action (delete), resource (ads), method (by inventory reference), and constraint (CPS campaigns only). It effectively distinguishes from sibling tools like ebay_bulk_delete_ads_by_listing_id.

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

Usage Guidelines3/5

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

The description includes a constraint ('CPS campaigns only') that helps narrow usage, but does not explicitly state when to use this tool versus alternatives or provide prerequisites. Minimal guidance beyond the constraint.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jyarbro/ebay-seller-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server