Skip to main content
Glama

Cancel My Offer

cancel_my_offer
Destructive

Cancels one of the caller's offers on a single XP listing -- 'pull my offer', 'cancel my bid'. An open offer resting across events is cancelled with cancel_my_open_offer. offer_uuid is the offer's bid_uuid or its buyer swap id. confirm=false returns a preview; confirm=true cancels it, and only that call returns success=true. Requires sign-in and the write:bids scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identifier": "<identifier>",
      "offer_uuid": "<offer_uuid>",
      "confirm": "<confirm>"
    },
    "name": "cancel_my_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesRequired. True to rescind; False to preview without rescinding.
identifierYesPublic listing identifier the offer was placed on.
offer_uuidYesIdentifier of the offer to cancel. Preferred: the offer's bid_uuid. Also accepted: its buyer swap identifier — MCP resolves it via privy-bids/mine.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / offer_uuid / description
      Previous value: -"Identifier of the offer to cancel. Preferred: bid_uuid from make_offer_on_listing's response. Also accepted: the buyer swap identifier from that same response — MCP resolves it via privy-bids/mine."New value: +"Identifier of the offer to cancel. Preferred: the offer's bid_uuid. Also accepted: its buyer swap identifier — MCP resolves it via privy-bids/mine."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description goes beyond them by disclosing the auth requirement (sign-in plus write:bids scope) and the asymmetric success signal ('only that call returns success=true' for confirm=true). The preview semantics of confirm=false also clarify that the destructive path is opt-in, not default.

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?

Purpose and the sibling distinction are front-loaded, followed by identifier guidance and the confirm semantics, with no filler sentences. Slightly dense with four distinct facts packed into one paragraph, but every clause carries information.

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?

For a 3-parameter destructive mutation with full schema coverage and an output schema, the description covers scope, the correct alternative, identifier resolution, the preview/commit split, and the auth prerequisite. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so confirm and offer_uuid are already documented in the schema, including the bid_uuid-or-buyer-swap-id fallback that the description repeats. The description adds essentially no meaning beyond the structured fields, so the baseline 3 applies.

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?

States a specific verb and resource ('Cancels one of the caller's offers on a single XP listing') and reinforces it with user-language synonyms ('pull my offer', 'cancel my bid'). It also names the boundary against the closest sibling, cancel_my_open_offer, so an agent can discriminate without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use-other rule: an offer resting across events goes to cancel_my_open_offer, while this tool handles a single-listing offer. It also spells out the preview-vs-commit flow via confirm=false/true, leaving no inference needed about which mode to call first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources