Skip to main content
Glama

ebay_bulk_delete_ads_by_inventory_reference

Remove multiple eBay ads in bulk using inventory references to streamline campaign management.

Instructions

Bulk delete ads by inventory reference through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesBulk delete ads by inventory reference request body
campaignIdYescampaignId required endpoint parameter
Behavior2/5

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

No annotations provided, so the description carries full burden. It states 'Bulk delete' but does not disclose whether the operation is destructive, idempotent, or has any side effects, rate limits, or permission requirements.

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 a single sentence of 13 words, which is concise. However, it lacks structure or front-loading of key information such as prerequisites or return behavior.

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?

For a bulk delete with nested input and no output schema, the description is too minimal. It fails to explain behavior on success, error handling, or whether the operation is atomic, leaving significant gaps for the agent.

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%: both parameters have basic descriptions. The tool's description adds no extra semantic value beyond what the schema already provides, resulting in a baseline score.

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 verb 'delete', resource 'ads', and the method 'by inventory reference', and identifies the API (eBay Marketing API). It effectively distinguishes from siblings 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 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 versus alternatives such as 'ebay_delete_ad', 'ebay_delete_ads_by_inventory_reference', or 'ebay_bulk_delete_ads_by_listing_id'. The description does not mention any conditions or prerequisites.

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/YosefHayim/ebay-mcp'

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