Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_get_ads_by_inventory_reference

Retrieve Cost Per Sale (CPS) ads for a specific SKU or inventory item group to analyze campaign performance by inventory reference.

Instructions

Get ads by inventory reference (SKU or inventory item group key). CPS campaigns only.

Input Schema

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

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

No annotations are provided, so the description carries the burden. It indicates a read operation ('Get') and scope ('CPS campaigns only'), but lacks details on common behaviors like pagination, permissions, or error handling. Basic transparency is present but not comprehensive.

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

Conciseness5/5

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

The description is a single concise sentence of 12 words, immediately front-loading the verb and resource. No filler or redundancy earns it a top score.

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?

There is no output schema, yet the description provides no information about return values or common behaviors such as pagination, error codes, or data format. For a tool with these gaps, the description is insufficiently complete.

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 clear descriptions for all three parameters. The description restates the inventory reference concept but does not add new meaning beyond the schema. Baseline score of 3 is appropriate as the schema already does the heavy lifting.

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 'Get', the resource 'ads', and the filtering criterion 'by inventory reference' (SKU or inventory item group key). It also specifies the scope 'CPS campaigns only', distinguishing it from siblings like 'ebay_get_ads' and 'ebay_get_ads_by_listing_id'.

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 explicitly limits usage to 'CPS campaigns only', providing clear context for when to use this tool. However, it does not name alternatives or give explicit when-not-to-use guidance, leaving the agent to infer from sibling tool names.

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/jyarbro/ebay-seller-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server