Skip to main content
Glama

ebay_create_ad

Create a single ad in an eBay campaign using a listing ID. Supports cost-per-sale and cost-per-click campaigns.

Instructions

Create a single ad in a campaign. Supports both CPS and CPC campaigns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesCampaign ID
adYesAd configuration
Behavior3/5

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

No annotations provided. Description adds that it supports CPS and CPC campaigns, which is behavioral context. However, it does not disclose other traits like whether the ad is created immediately, idempotency, or response behavior. Schema covers adGroupId condition but description omits it.

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?

Single sentence of 10 words, front-loaded with action. Every word earns its place; no unnecessary fluff.

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 complexity (nested object, two campaign types, many sibling tools) and absence of output schema, the description is too brief. It should mention conditional requirements (e.g., adGroupId for CPC) and what the return value contains (e.g., ad ID). Lacks sufficient context for an AI agent to use correctly without referencing schema.

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%; all properties have descriptions. The tool description does not add any extra meaning beyond the schema for the parameters. Baseline score of 3 applies.

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?

Description clearly states 'Create a single ad in a campaign' with specific verb and resource. It also specifies support for both CPS and CPC campaigns, distinguishing it from bulk ad creation tools among siblings.

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_bulk_create_ads_by_inventory_reference or ebay_clone_ad. No prerequisites (e.g., campaign must exist) or conditional requirements mentioned.

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