Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_create_keyword

Create a keyword for manual targeting in a CPC campaign ad group by specifying text, match type, and optional bid override.

Instructions

Create a keyword for manual targeting in a CPC campaign ad group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesKeyword configuration
campaignIdYesCampaign ID
Behavior2/5

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It only states the action 'Create' but does not address idempotency, overwrite behavior, error conditions, or required permissions. The agent lacks insight into the tool's side effects or constraints.

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, which is concise and to the point. It is front-loaded with the action and resource. However, it could be more structured (e.g., bullet points) to improve readability, especially given the nested parameters.

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 tool's complexity (nested objects, 2 parameters) and lack of output schema, the description is incomplete. It does not mention what the tool returns (e.g., the created keyword ID) or any side effects. The agent would lack essential operational context.

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%, so the baseline is 3. The description adds no extra meaning beyond the schema; it does not explain the nested keyword object or the optional bid parameter. The description's simplicity means it does not hinder understanding but also does not enhance it.

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 a keyword for manual targeting within a CPC campaign ad group. It specifies the resource (keyword) and the context (CPC campaign ad group), making the purpose clear. However, it does not differentiate from sibling tools like ebay_bulk_create_keywords, which could lead to confusion about when to use this single-keyword variant.

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 is provided on when to use this tool versus alternatives, such as bulk creation tools or updating existing keywords. There is no mention of prerequisites (e.g., campaign and ad group must exist) or any scenario-specific recommendations.

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