Skip to main content
Glama

Reject Offer

reject_offer
Destructive

Rejects one buyer's offer on the caller's own listing on XP -- 'reject the lowball offer on my tickets'. confirm=false returns a preview of the offer; confirm=true rejects it, and only that call returns success=true. identifier and offer_uuid come from get_my_listing_status. Requires sign-in and the write:listings 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": "reject_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesRequired. True to reject the offer; False to preview without rejecting.
identifierYesPublic listing identifier from list_my_listings or get_my_listing_status.
offer_uuidYesOffer UUID from get_my_listing_status open_offers.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/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, but the description adds real value on top: it explains the two-mode confirm semantics, notes that only confirm=true returns success=true, and discloses the sign-in plus write:listings scope requirement. These are exactly the auth and irreversibility details an agent needs before a destructive call.

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?

Three compact sentences, each carrying distinct information: what it does, the confirm preview/reject split, and the parameter sourcing plus auth prerequisites. No filler and the destructive semantics are front-loaded.

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?

With an output schema present, return values need no explanation, and the description covers the remaining gaps an agent would care about — auth scope, parameter origin, and the preview-versus-commit behavior of a destructive tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by documenting provenance for identifier and offer_uuid (get_my_listing_status) and clarifying that confirm=true is the only path returning success=true. It adds meaning beyond the field descriptions rather than restating them.

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 ("Rejects one buyer's offer") and narrows scope to "the caller's own listing on XP," which separates it from accept_offer and the various cancel_* tools. The quoted user phrasing ("reject the lowball offer on my tickets") makes the intent unmistakable.

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?

Gives clear operational guidance: use confirm=false to preview, confirm=true to actually reject, and pull identifier/offer_uuid from get_my_listing_status. It doesn't explicitly name accept_offer as the counterpart action or state when not to reject, so it stops just short of full when/when-not coverage.

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