Skip to main content
Glama

ebay_bulk_cancel_packages

Cancel multiple eBay packages in one request to simplify order cancellation workflows.

Instructions

Cancel multiple packages in one request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bulkCancelRequestYesBulk cancel request data
Behavior2/5

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

With no annotations, the description must disclose behavioral details but only states 'cancel multiple packages'. It omits whether cancellation is reversible, affects shipping status, triggers refunds, or requires specific permissions. This lack of transparency could lead to misuse.

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 one sentence, making it concise, but it sacrifices necessary detail. A longer description could provide crucial context without being bloated, so it is not optimally concise for decision-making.

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 the tool's complexity (nested object parameter, no output schema, large sibling set), the description is insufficient. It does not explain the meaning of cancellation, expected payload structure, or side effects, making it incomplete for reliable agent 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 single parameter 'bulkCancelRequest' is described in the schema as 'Bulk cancel request data', and the tool description adds no further clarification. While schema description coverage is 100%, the description does not specify expected properties within the nested object, leaving its structure ambiguous.

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?

The description clearly states the verb 'cancel' and resource 'multiple packages' in one request. However, it does not differentiate from siblings like 'ebay_bulk_delete_packages' or 'ebay_cancel_package', leaving ambiguity about the semantic difference between cancel and delete.

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 is provided on when to use this tool versus alternatives, such as singular cancellation or other bulk actions. The description does not mention prerequisites, constraints, or typical use cases, leaving the agent without context for selection among many sibling tools.

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