Skip to main content
Glama

ebay_get_campaign_negative_keywords

Retrieve all negative keywords assigned to an eBay campaign to prevent ads from showing for irrelevant search terms.

Instructions

Get all campaign-level negative keywords.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesCampaign ID
limitNoMaximum number of results to return
offsetNoNumber of results to skip
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action without disclosing read-only nature, permissions, rate limits, or any behavioral traits. The agent gains minimal insight beyond the name.

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?

A single sentence with no waste. Efficient but lacks structure or additional context. Could be slightly expanded with usage notes without harming 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?

There is no output schema, so the description should explain what is returned (e.g., a list of negative keywords). It does not mention pagination, response format, or how to use the offset/limit parameters in practice. The agent is left guessing about the output.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond what is already in the schema for the three parameters (campaignId, limit, offset).

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 action (Get) and the resource (campaign-level negative keywords), and the plural 'all' distinguishes it from the singular sibling tool 'get_campaign_negative_keyword'. However, it does not specify that results are paginated or the scope beyond campaignId.

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 like 'get_campaign_negative_keyword' (singular) or bulk variants. The agent must infer from tool names 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