Skip to main content
Glama

place_bid

Place a bid on an eBay auction item by entering the item ID, maximum bid amount in USD, and your eBay username and password.

Instructions

Place a bid on an eBay auction item. Requires eBay credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYeseBay auction item ID
passwordYeseBay password
usernameYeseBay username or email
bid_amountYesMaximum bid amount in USD
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only notes the credential requirement, but omits critical details such as the bid being binding, potential fees, success/failure handling, or the effect on the user's account.

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

Conciseness5/5

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

The description is a single, front-loaded sentence that immediately states the purpose and a key requirement. There is no wasted verbiage.

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?

This is a financially significant mutation tool with no annotations or output schema. The description is far too sparse: it fails to mention binding obligations, possible outcomes, error behavior, or what the response will look like. Significant context is missing for an AI agent to safely invoke it.

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?

The schema covers 100% of parameters with descriptions, providing a baseline of 3. The description adds a small note about credentials, reinforcing the username/password fields, but does not materially enrich understanding of the bid_amount or item_id beyond what the schema already states.

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 with a specific verb ('Place') and resource ('a bid on an eBay auction item'). It distinguishes itself from sibling tools like buy_it_now by focusing on auction bidding.

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 like buy_it_now. It only states that eBay credentials are required, but does not mention when placing a bid is appropriate or when other tools should be used.

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/markswendsen-code/mcp-ebay'

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