Skip to main content
Glama

ebay_update_campaign_negative_keyword

Update a campaign's negative keyword by changing its text and match type to refine ad targeting.

Instructions

Update a campaign-level negative keyword.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesCampaign ID
negativeKeywordIdYesNegative Keyword ID
updateDataYesNegative keyword update data
Behavior2/5

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

The description lacks any behavioral details beyond the generic 'Update'. No annotations are provided, so the agent has no information about idempotency, side effects, required permissions, or whether the update is incremental or full replacement. This is insufficient 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 extremely concise at only six words, which is efficient but potentially overly terse given the lack of usage guidance. It front-loads the purpose, but sacrifices completeness for brevity.

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 large number of sibling tools, the description should clarify the scope (single vs. bulk) and any constraints. There is no output schema, and annotations are absent. The tool modifies data but provides no behavioral context, making it insufficient for safe invocation.

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 for all three parameters, including the nested structure. The description adds no additional meaning beyond what is already in the schema, so a baseline score of 3 is appropriate.

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 specific action ('Update') and resource ('campaign-level negative keyword'), distinguishing it from related tools like create or delete. However, it does not explicitly differentiate from bulk variants like 'ebay_bulk_update_campaign_negative_keywords', which could cause confusion.

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 (e.g., bulk update or creating/deleting). No prerequisites, limitations, or context of use are provided, leaving the agent to infer usage from the tool name alone.

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