Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_find_campaign_by_ad_reference

Read-only

Find the eBay marketing campaign tied to a specific ad reference. Use listing ID or inventory reference to retrieve campaign details through the Marketing API.

Instructions

Find campaign by ad reference through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listingIdNolistingId optional endpoint parameter
inventoryReferenceIdNoinventoryReferenceId optional endpoint parameter
inventoryReferenceTypeNoinventoryReferenceType optional endpoint parameter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.14.1
    • changedInput schema / properties / inventoryReferenceId / description
      Previous value: -"SKU or inventory item group key"New value: +"inventoryReferenceId optional endpoint parameter"
    • changedInput schema / properties / inventoryReferenceType / description
      Previous value: -"Reference type"New value: +"inventoryReferenceType optional endpoint parameter"
    • removedInput schema / properties / inventoryReferenceType / enum
      Removed value: -[
-  "INVENTORY_ITEM",
-  "INVENTORY_ITEM_GROUP"
-]
    • changedInput schema / properties / listingId / description
      Previous value: -"eBay listing ID"New value: +"listingId optional endpoint parameter"
  2. First observedv1.8.10

TDQS

C2.9/5.0
Behavior2/5

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

The readOnlyHint annotation already covers the safety profile, but the description adds little beyond 'through the eBay Marketing API.' It does not disclose output shape, matching behavior, or whether any parameter is required, so it contributes minimal behavioral context beyond the annotation.

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

Conciseness4/5

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

The description is a single, efficient sentence with no wasted words, and the key operation is front-loaded. It is concise without being rambling, though the brevity comes at the cost of needed detail.

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?

With three optional parameters and no output schema, an agent needs to know which parameter(s) constitute the ad reference, whether they are alternatives, and what the response contains. None of that is present, leaving the tool under-specified for correct 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?

Schema description coverage is 100%, so the baseline is 3. However, the schema descriptions are tautological ('listingId optional endpoint parameter') and the tool description does not clarify how 'ad reference' maps to the parameters or whether listingId and inventoryReference* are interchangeable.

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 states a specific verb ('Find'), resource ('campaign'), and qualifier ('by ad reference'), making the core purpose clear. It does not explicitly distinguish itself from sibling lookup tools like ebay_get_campaign or ebay_get_campaign_by_name, so it falls short of a 5.

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?

There is no guidance on when to use this tool over ebay_get_campaign, ebay_get_campaign_by_name, or generic search/fetch. It also does not explain whether listingId and inventoryReferenceId are alternatives or must be combined, leaving invocation choices ambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools