Skip to main content
Glama

ebay_get_ads_by_inventory_reference

Retrieve ads linked to a specific inventory reference within an eBay campaign. Provide campaign ID, inventory reference ID, and inventory reference type to fetch ad data.

Instructions

Get ads by inventory reference through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYescampaignId required endpoint parameter
inventoryReferenceIdYesinventoryReferenceId required endpoint parameter
inventoryReferenceTypeYesinventoryReferenceType required endpoint parameter
Behavior1/5

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

The description does not disclose any behavioral traits. It lacks information on side effects, required permissions, rate limits, or what the response contains. Since no annotations are provided, the description carries the full burden but fails to provide any transparency beyond the bare operation name.

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. However, it is too brief to be informative and essentially restates the tool name. Brevity without substance does not earn a higher score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of an output schema, the description should hint at the return format or data structure. It does not. Additionally, with many sibling tools, more context about the inventory reference concept and how this tool fits into the workflow is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the parameter descriptions are tautological (e.g., 'campaignId required endpoint parameter') and add no meaning beyond the name and requirement. The tool description does not compensate by explaining what each parameter represents or how they relate to the inventory reference concept.

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 and resource: 'Get ads by inventory reference'. This distinguishes it from sibling tools like ebay_get_ads (which might retrieve all ads) and ebay_bulk_create_ads_by_inventory_reference (which creates). However, it does not explain what an 'inventory reference' is, leaving some ambiguity.

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 ebay_get_ads, ebay_get_campaign_by_name, or the bulk creation tools. There is no mention of use cases, prerequisites, or when not to use it.

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