Skip to main content
Glama

ebay_find_campaign_by_ad_reference

Locate an eBay promotion campaign by providing a listing ID or inventory reference details. Use SKU or item group key to identify the campaign.

Instructions

Find a campaign by listing ID or inventory reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inventoryReferenceIdNoSKU or inventory item group key
inventoryReferenceTypeNoReference type
listingIdNoeBay listing ID
Behavior2/5

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

Lacking annotations, the description must disclose behavior but only states the action. No mention of side effects, permissions, rate limits, or whether the operation is read-only. The agent is left uninformed about safe usage.

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 single sentence is concise but lacks structure. It front-loads the action but omits any additional context. Could be expanded slightly without losing 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?

For a find operation with 3 optional parameters and no output schema, the description is too sparse. It doesn't explain return format, parameter interactions, or typical use cases. Leaves gaps for the agent.

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% so parameters are documented. The description adds no extra meaning beyond the schema, such as how to combine parameters or that they are alternatives. 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 it finds a campaign by listing ID or inventory reference, which matches the tool name and parameter schema. It distinguishes itself from sibling tools like `ebay_get_campaign` (which likely finds by campaign ID) and `ebay_get_campaign_by_name`.

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 on when to use this tool versus alternatives like `ebay_get_campaign` or `ebay_search_campaigns`. The description gives no context about prerequisites or mutually exclusive parameter usage.

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