Skip to main content
Glama
jyarbro

eBay Seller MCP Server

by jyarbro

ebay_update_ad_rate_strategy

Update the bid percentage for a Cost Per Sale campaign to adjust your ad rate strategy.

Instructions

Update the ad rate strategy for a CPS campaign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
strategyYesAd rate strategy
campaignIdYesCampaign ID
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. The word 'update' implies mutation, but there is no mention of side effects, required permissions, or whether the change takes effect immediately. Without annotation support, the description fails to inform the agent about the tool's safety or behavior beyond the basic action.

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 a single sentence of nine words, very concise and to the point. However, it may be too terse, lacking necessary context. Still, it earns a 4 for efficiency.

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?

Despite having only two parameters and no output schema, the description omits crucial context: what CPS stands for, what the return value is (if any), and error conditions. The tool is a mutation, so the agent needs to know if it returns the updated strategy or just acknowledges success. The description is insufficient for complete understanding.

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 each parameter is described in the schema. The description does not add extra semantic value beyond what the schema already provides (campaignId, strategy with bidPercentage). The baseline 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 'Update the ad rate strategy for a CPS campaign' clearly states the verb (update) and the resource (ad rate strategy for a CPS campaign). It distinguishes this tool from sibling update tools like ebay_update_ad_bid or ebay_update_bidding_strategy, which target different aspects of campaigns. However, it could be more specific about what 'ad rate strategy' entails.

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 instead of alternatives (e.g., when to use ebay_update_bidding_strategy vs. this). There is no mention of prerequisites (e.g., campaign type must be CPS) or integration with other tools. Given the many sibling update tools, this is a significant gap.

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/jyarbro/ebay-seller-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server