Skip to main content
Glama

ebay_suggest_keywords

Get keyword suggestions for an eBay ad group by providing campaign and ad group IDs. Returns relevant keywords derived from listings.

Instructions

Get keyword suggestions for an ad group. Returns relevant keywords based on listings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesCampaign ID
adGroupIdYesAd Group ID
Behavior3/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. The description indicates a read operation ('Get keyword suggestions') with no side effects. However, it does not elaborate on potential performance implications, rate limits, or any other behavioral traits beyond the basic purpose.

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 concise, consisting of two sentences. The first sentence clearly states the purpose, and the second adds a brief note on the source of suggestions. No unnecessary information is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, yet the description does not specify the structure or format of the returned keyword suggestions. For a suggestion tool, providing information about the output would improve completeness. Additionally, no mention of pagination or limits.

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 'Campaign ID' and 'Ad Group ID'. The description does not add any meaning beyond these schema descriptions, maintaining the baseline of 3. No additional context on how these IDs are used.

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 tool's action ('Get keyword suggestions') and its context ('for an ad group', 'based on listings'). This distinguishes it from sibling tools like ebay_suggest_bids, ebay_suggest_budget, etc., which focus on other types of suggestions.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or conditions. Given the existence of multiple suggestion tools, explicit usage context would be beneficial.

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