Skip to main content
Glama

ebay_get_item_promotion

Retrieve detailed information about a specific eBay item promotion using its promotion ID. Get promotion status, discounts, and eligible items.

Instructions

Get details of a specific item promotion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promotionIdYesPromotion ID
Behavior1/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It merely states 'Get details' without specifying whether the tool is read-only, what data is returned, pagination, error conditions, or any side effects. This is insufficient for an agent to understand the tool's behavior.

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, which is concise but lacks depth. While not verbose, it omits useful details that could fit in a few more words, such as the scope of the details or any special requirements.

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 simplicity (1 parameter, no output schema), the description is minimal. However, in a large sibling group with many promotion-related tools, the lack of differentiation and behavioral context makes it incomplete for effective agent use.

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 covers 100% of parameters with a description ('Promotion ID'). The tool description adds no additional meaning beyond what the schema already provides. Per guidelines, baseline 3 applies when schema coverage is high.

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 'Get' and resource 'item promotion', making the basic purpose obvious. However, it does not differentiate from sibling tools like 'ebay_get_item_price_markdown_promotion' or 'ebay_get_promotions', leaving ambiguity about which tool to use for which type of promotion.

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?

The description provides no guidance on when to use this tool vs. other promotion-related tools. It lacks context on prerequisites, alternatives, or typical scenarios, leaving the agent to infer usage from the name alone.

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