Skip to main content
Glama

ebay_suggest_items

Suggest items for eBay Marketing campaigns by providing a campaign ID, with optional filters for category, limit, and offset.

Instructions

Suggest items through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNolimit optional endpoint parameter
offsetNooffset optional endpoint parameter
campaignIdYescampaignId required endpoint parameter
categoryIdsNocategoryIds optional endpoint parameter
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Suggest items' without mentioning side effects, permissions, rate limits, or response format. This is insufficient for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise at one sentence, but it is under-specified and lacks structure. It is not overly long, but the brevity results in missing crucial information.

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

Completeness1/5

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

Given the complexity of the eBay API and the large number of sibling tools, the description is severely incomplete. It fails to explain the tool's functionality, response, or relationship to other tools. No output schema exacerbates the gap.

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 schema already documents parameters. The description adds no additional meaning beyond the schema's basic parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb 'suggest' and resource 'items' but is vague about what 'suggest items' means. It does not differentiate from sibling tools like ebay_find_eligible_items or ebay_suggest_keywords. The purpose is unclear.

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 vs alternatives. The description is too short to provide context for usage decisions among many similar sibling tools.

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