Skip to main content
Glama

place_bid

Set a proxy bid ceiling on an eBay auction; your bid automatically increases up to the specified maximum to outbid competitors.

Instructions

Place a proxy bid on an eBay auction.

Trading API PlaceOffer with Action=Bid. eBay treats max_bid_amount as a proxy ceiling — it bids the minimum needed to outbid the current high bidder, and continues raising up to max_bid_amount as competing bids come in.

PRODUCTION HOST WARNING: when the active host is "production", a successful call commits real money on eBay. Inspect server_info() or list_hosts() before committing.

Args: item_id: numeric eBay item ID. Get from search() or get_item(). max_bid_amount: the proxy bid ceiling in currency. Must be > 0. confirm_amount: must equal max_bid_amount exactly. The repeated dollar amount is a safety gate against typos. quantity: number of units (default 1; only relevant for multi-quantity auctions). currency: ISO currency code matching the listing (default "USD"). Must match the listing's currency or eBay refuses. max_bid_override: optional ceiling that authorizes amounts above the $500 per-call safety cap. Pass a value >= max_bid_amount to bypass the cap for this call. Lower values are refused. host: configured host name. Defaults to default_host. The active host (sandbox vs production) is surfaced in the response.

Returns: On success: dict with host, item_id, action="Bid", amount, currency, placed=True, current_price, minimum_to_outbid, high_bidder, and (on production) a warning field. On safety-gate failure: structured refusal payload (refused=True, reason, message, plus the offending values). Raises ValueError on empty item_id, non-positive amounts, etc. On eBay-side errors (listing ended, currency mismatch, insufficient bid, etc.) raises TradingApiError.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes
max_bid_amountYes
confirm_amountYes
quantityNo
currencyNoUSD
max_bid_overrideNo
hostNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description carries full burden. Thoroughly explains proxy bid mechanics, safety gates, host differentiation, error handling, and return values.

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?

Well-structured with purpose first, followed by mechanism, warnings, parameter list, and return values. Informative without excessive verbosity.

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

Completeness5/5

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

Covers all aspects: purpose, mechanism, parameters, return values, errors, safety, and host context. Refers to sibling tools for host checking. Complete for a complex bidding tool.

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

Parameters5/5

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

Schema description coverage is 0%, but description explains each parameter with purpose, constraints, and interactions (e.g., confirm_amount as safety gate, max_bid_override for exceeding cap). Adds significant meaning beyond schema types.

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?

Clearly states 'Place a proxy bid on an eBay auction', using specific verb and resource. Distinguishes from sibling tools like buy_now and make_best_offer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context of proxy bidding and host safety, but lacks explicit when-to-use vs alternatives. Sibling context makes scope clear.

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

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