Skip to main content
Glama

ebay_bulk_create_campaign_keyword

Bulk add keywords to an eBay campaign by providing a campaign ID and an array of keyword definitions, each with text, match type, and optional bid.

Instructions

Bulk create keywords at the campaign level.

Input Schema

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a bulk create operation but fails to describe key traits like idempotency, error handling for partial failures, maximum batch size, required permissions, or any side effects. This is a significant gap for a mutation tool.

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 sentence with no wasted words. It is front-loaded with the key action and scope. However, given the complexity of the nested schema and the lack of other explanatory text, it could be slightly expanded without compromising 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?

The tool has 2 required parameters, a nested object, and no output schema. The description does not mention the return value, error behavior, or constraints like maximum number of keywords per request. It misses critical context for effective agent use.

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% with descriptions for all properties. The description adds no additional meaning beyond what the schema provides, so it meets the baseline of 3. It does not clarify the structure of 'bid' or the meaning of 'matchType' options, but the schema already covers these.

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 the tool creates keywords in bulk at the campaign level. However, it does not explicitly distinguish itself from sibling tools like 'ebay_bulk_create_keywords' (which may target ad groups) or 'ebay_create_keyword' (single creation). The phrase 'at the campaign level' provides some differentiation but could be more explicit.

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 such as 'ebay_bulk_create_keywords', 'ebay_create_keyword', or 'ebay_bulk_create_campaign_negative_keywords'. No mention of prerequisites, limits, or scenarios where this tool is preferred.

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