Skip to main content
Glama

ebay_delete_ads_by_inventory_reference

Delete ads from a CPS campaign using an inventory reference (SKU or item group key).

Instructions

Delete ads by inventory reference for a CPS campaign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesCampaign ID
inventoryReferenceIdYesSKU or inventory item group key
inventoryReferenceTypeYesReference type
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Delete ads' without mentioning irreversibility, required permissions, rate limits, or side effects. This is a significant gap for a delete operation.

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 8-word sentence, very concise. However, it lacks critical details, making it under-informative rather than efficiently concise.

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 delete operation with 3 required params and no output schema, the description is incomplete. It omits return value, error conditions, preconditions (e.g., existing campaign and ads), and does not leverage sibling tools for context.

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 all three parameters. The description adds no additional meaning beyond the schema, which already explains campaignId, inventoryReferenceId, and inventoryReferenceType. Baseline score of 3 is appropriate.

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

Purpose4/5

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

Description 'Delete ads by inventory reference for a CPS campaign' clearly states action (delete), resource (ads), and scope (by inventory reference for CPS campaign). It distinguishes from siblings like ebay_delete_ad (single ad by ID) and ebay_bulk_delete_ads_by_inventory_reference (bulk). However, 'CPS campaign' is not explained, and no explicit sibling comparison is provided.

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 usage guidance is given. The description does not indicate when to use this tool versus alternatives like ebay_bulk_delete_ads_by_inventory_reference or ebay_delete_ad, nor any prerequisites or exclusions.

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