Skip to main content
Glama

ebay_bulk_create_keywords

Add multiple keywords to an eBay ad campaign in one request, specifying match type and bid for each keyword.

Instructions

Create multiple keywords in a campaign. Maximum recommended per call varies by eBay.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesCampaign ID
adGroupIdYesAd Group ID
keywordsYesBulk keyword creation request
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a write operation ('Create') and hints at per-call limits, but does not disclose idempotency, partial failure behavior, rate limits, or authentication requirements beyond the basic action.

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 extremely concise with two sentences that front-load the main action. However, it sacrifices necessary detail for brevity, earning a high score for conciseness but not penalizing for missing content as that is captured in other dimensions.

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 the input schema (nested objects, 3 required parameters) and the absence of an output schema and annotations, the description is incomplete. It does not explain how to structure the keywords array, constraints on matchType, or what the response contains.

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?

The input schema has 100% description coverage (each property has a description), so the baseline is 3. The description does not add any additional parameter-level details beyond what the schema already provides, such as formatting or constraints.

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 clearly states 'Create multiple keywords in a campaign,' which specifies the action and resource. It distinguishes from 'ebay_create_keyword' (single) and other bulk operations. However, the mention of 'Maximum recommended per call varies by eBay' is vague, lacking specific limits.

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 explicit guidance on when to use this tool vs alternatives like 'ebay_create_keyword' for single keywords. The description does not provide when-not-to-use scenarios or mention sibling tools for comparison.

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