Skip to main content
Glama

ebay_suggest_max_cpc

Suggest maximum cost-per-click bids for your eBay listings to improve advertising campaign performance.

Instructions

Suggest max cpc through the eBay Marketing API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYesSuggest max cpc request body
Behavior1/5

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

With no annotations, the description carries full burden for behavioral transparency. It only says 'through the eBay Marketing API', which is trivial. No mention of idempotency, rate limits, data mutability, or what happens when no suggestions are available.

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

Conciseness2/5

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

The description is a single short sentence, which is concise but overly vague. It fails to earn its place by providing meaningful information beyond the tool name.

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?

The description is severely incomplete given the absence of annotations and output schema. It does not explain the return value, error conditions, or how the suggestion is computed. The nested parameter structure is left unclarified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no parameter-level guidance. The schema has a single parameter 'request' with a generic description that echoes the tool purpose. Nested fields 'listingIds' and 'marketplaceId' lack descriptions, and the tool description does not explain their semantics or valid values.

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 it suggests max cpc via the eBay Marketing API. The verb 'suggest' and resource 'max cpc' are specific, and the name distinguishes it from sibling suggest tools (e.g., suggest_bids, suggest_keywords). However, it could be more explicit about what 'max cpc' means and for which entities.

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 other suggestion tools like ebay_suggest_budget or ebay_suggest_bids. The description does not provide context about prerequisites, typical use cases, or alternatives.

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