Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_create_ad_group_negative_keyword

Create a negative keyword at the ad group level to block ads from showing for that keyword within the campaign and ad group.

Instructions

Create an ad group-level negative keyword. Prevents ads in this ad group from showing for this keyword.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adGroupIdYesAd Group ID
campaignIdYesCampaign ID
negativeKeywordYesNegative keyword configuration
Behavior2/5

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

With no annotations, the description must fully convey behavioral traits. It only states the core effect (prevents ads), but lacks details on idempotency, error handling, duplicate handling, permissions, or what happens if the keyword already exists.

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?

Two sentences, front-loaded with action and effect, no extraneous words. Efficient and to the point.

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?

No output schema; creation tools typically need to indicate what is returned (e.g., success status, created keyword). Also missing prerequisites (e.g., campaign and ad group must exist). Given nested parameters and enum, more context is needed.

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 schema already documents all three parameters. The description adds no additional meaning to the parameters, thus 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?

The description clearly states the verb ('Create'), the resource ('ad group-level negative keyword'), and the effect ('Prevents ads in this ad group from showing for this keyword'). This distinguishes it from sibling tools like ebay_create_campaign_negative_keyword.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/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 versus alternatives like ebay_bulk_create_ad_group_negative_keywords or ebay_create_campaign_negative_keyword. The usage context is implied but not stated, leaving the agent to infer.

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