Skip to main content
Glama

Create, Edit, Validate, Fee-Preview, Re-Expose or Terminate Seller Offers

aukro_manage_offer
Destructive

Prepare, validate, create, modify, terminate, or reexpose Aukro.cz seller offers and preview listing fees via authenticated API actions.

Instructions

Manage your seller listings on Aukro.cz using the v2 Offers API: prepare edit payload from an existing offer (PREPARE_EDIT), validate an offer form (VALIDATE), calculate listing fees (FEE_PREVIEW), create a new offer (CREATE), modify an active offer (MODIFY), terminate an offer early (TERMINATE), or re-expose ended offers (REEXPOSE). Requires authentication.

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": {
      "action": "<action>"
    },
    "name": "aukro_manage_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesSeller offer management action
offerIdNoNumeric offer ID (for `PREPARE_EDIT`, `MODIFY`, `TERMINATE`)
offerIdsNoList of numeric offer IDs (for bulk `TERMINATE` or `REEXPOSE`)
offerPayloadNoOffer form payload (`createItemFormDto` / `modifyItemFormDto` / `feePreviewRequest`)
terminateReasonNoOptional reason when terminating an offer early

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is largely covered; the description adds the authentication requirement and the API version. It does not differentiate which actions are effectively read-only preparations (VALIDATE, FEE_PREVIEW, PREPARE_EDIT) versus irreversible ones (TERMINATE, REEXPOSE), nor what a fee preview returns, so meaningful behavioral context is still missing for a tool with a destructive hint of such coarse granularity.

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?

A single dense sentence that is front-loaded with the core purpose and then uses parenthetical action labels, which read efficiently rather than as filler. It is long only because there are seven actions to enumerate; nothing is genuinely wasteful, though sub-bullets or a second sentence separating read-like from destructive actions would improve scannability.

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

Completeness3/5

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

This is a complex, state-changing tool with seven actions, a nested free-form offerPayload object, and no output schema. The description covers action selection and authentication, but leaves the payload structure (createItemFormDto / modifyItemFormDto / feePreviewRequest) entirely to the schema's opaque type names, and does not say which actions require which payload or ID fields.

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 the enum values and per-field notes (offerId for PREPARE_EDIT/MODIFY/TERMINATE, offerIds for bulk TERMINATE/REEXPOSE) already carry the parameter meaning. The description adds no syntax, format, or mapping detail beyond what the schema states, so the baseline of 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 ('Manage your seller listings on Aukro.cz using the v2 Offers API') and then enumerates all seven operations (PREPARE_EDIT, VALIDATE, FEE_PREVIEW, CREATE, MODIFY, TERMINATE, REEXPOSE). An agent can immediately tell this is the seller-side mutation tool, distinct from read-oriented siblings like aukro_search_offers or aukro_get_offer_detail.

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?

Each action string is paired with a plain-language purpose ('prepare edit payload from an existing offer', 'calculate listing fees', 'terminate an offer early', 're-expose ended offers'), which effectively maps needs to actions. However, it never names alternatives (e.g. when to use aukro_offer_templates instead of CREATE, or aukro_my_sales instead of MODIFY), nor any prerequisite beyond authentication.

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