Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_create_ad

Create a single ad in an eBay campaign for CPS or CPC campaigns. Requires campaign ID and listing ID.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adYesAd configuration
campaignIdYesCampaign ID
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only states the action ('create') and supported campaign types. It omits details like authentication requirements, rate limits, idempotency, or consequences of duplicate creation. The mutation nature is implied but not elaborated.

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 extremely concise with two sentences, front-loading the purpose. Every word is necessary, and there is no fluff or repetition.

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 of a creation tool with a nested object and no output schema, the description is insufficient. It does not explain campaign types (CPS/CPC), return values, error handling, or behavior on duplicate ad creation. The description leaves key contextual gaps.

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 schema already explains parameters. The tool description adds no extra meaning beyond what is in the schema. Baseline 3 is appropriate as the description does not hinder but also does not enhance understanding.

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 action ('create'), the resource ('single ad in a campaign'), and differentiates from bulk creation siblings like ebay_bulk_create_ads_by_listing_id. It also specifies supported campaign types (CPS and CPC), providing useful context.

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?

The description lacks guidance on when to use this tool versus alternatives. It mentions campaign types but does not explain when to prefer this over bulk creation or other ad-related tools. No exclusions or prerequisites are stated.

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