Skip to main content
Glama

ebay_bulk_delete_ads_by_listing_id

Delete multiple eBay ads from CPS campaigns by providing listing IDs.

Instructions

Delete multiple ads by listing ID. CPS campaigns only.

Input Schema

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

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

No annotations are provided, so the description must cover behavioral traits. It states 'Delete multiple ads' indicating a destructive action, but lacks details on side effects, permissions, error handling, or constraints like batch size. This is insufficient for an agent to understand the full impact.

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

Conciseness4/5

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

The description is extremely concise at one sentence, front-loading the key action. While it is efficient, it sacrifices some useful context that could be added without becoming verbose. Still, it meets the bar for conciseness.

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 no annotations, the description is incomplete for a bulk delete operation. It does not mention success/error responses, rate limits, maximum number of listing IDs, or prerequisites. An agent would lack essential context for reliable invocation.

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?

The input schema already describes both parameters ('Campaign ID' and 'Array of listing IDs to delete') with 100% coverage. The description adds no new semantic meaning beyond reinforcing 'by listing ID'. Per guidelines, 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 verb 'Delete', the resource 'ads', and the method 'by listing ID'. It also specifies 'CPS campaigns only', which distinguishes it from similar sibling tools that may operate on other campaign types.

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

Usage Guidelines4/5

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

The description provides a clear usage context: only for CPS campaigns. However, it does not explicitly state when not to use this tool or mention alternative tools for other campaign types. Still, the guidance is sufficient for an informed agent.

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