Skip to main content
Glama
elchin92

Avito MCP

by elchin92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delivery: cancel announcement [3PL]

delivery_cancel_announcement_3pl
Destructive

Cancel an existing third-party logistics (3PL) delivery announcement. Irreversibly stops the shipment and prevents further processing. Use to abort a pending delivery.

Instructions

[3PL] Cancels a previously created shipment announcement in the delivery service. Irreversibly cancels an announcement created via delivery_create_announcement_3pl. The method is implemented on the delivery-service side — on a regular seller account it returns 403/404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNov0.7.0: if true — returns a preview of the HTTP request without calling the Avito API. Safe for inspecting exactly what would be done. Default: the value of AVITO_MCP_DRY_RUN_DEFAULT (usually false).
reasonNoCancellation reason (optional).
announcementIDYesIdentifier of the announcement to cancel (required).
idempotencyKeyNov0.7.0: optional key for duplicate protection. A repeat call with the same key within AVITO_MCP_IDEMPOTENCY_TTL_SEC returns the cached result. The same key with different args returns a conflict error. Keys are stored as bounded SHA-256 fingerprints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.3
  2. Removedv1.3.2
  3. Changed7 schema fields changedv1.2.0
    • removedInput schema / properties / announcementID / additionalProperties
      Removed value: -{}
    • addedInput schema / properties / announcementID / format
      Added value: +"uuid"
    • addedInput schema / properties / announcementID / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / announcementID / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • changedInput schema / properties / announcementID / type
      Previous value: -"object"New value: +"string"
    • changedInput schema / properties / idempotencyKey / description
      Previous value: -"v0.7.0: optional key for duplicate protection. A repeat call with the same key within AVITO_MCP_IDEMPOTENCY_TTL_SEC returns the cached result. The same key with different args returns a conflict error — this is safe by design."New value: +"v0.7.0: optional key for duplicate protection. A repeat call with the same key within AVITO_MCP_IDEMPOTENCY_TTL_SEC returns the cached result. The same key with different args returns a conflict error. Keys are stored as bounded SHA-256 fingerprints."
    • addedInput schema / properties / reason / enum
      Added value: +[
+  "CANCELED_BY_DELIVERY_PROVIDER",
+  "CANCELED_BY_AVITO"
+]
  4. Changed4 schema fields changedv0.8.0
    • changedInput schema / properties / announcementID / description
      Previous value: -"См. AnnouncementID в swaggers/Доставка.json"New value: +"Identifier of the announcement to cancel (required)."
    • changedInput schema / properties / dryRun / description
      Previous value: -"v0.7.0: если true — возвращает preview HTTP-запроса без вызова Avito API. Безопасно для просмотра, что именно будет сделано. Default: значение AVITO_MCP_DRY_RUN_DEFAULT (обычно false)."New value: +"v0.7.0: if true — returns a preview of the HTTP request without calling the Avito API. Safe for inspecting exactly what would be done. Default: the value of AVITO_MCP_DRY_RUN_DEFAULT (usually false)."
    • changedInput schema / properties / idempotencyKey / description
      Previous value: -"v0.7.0: опциональный ключ для защиты от дублей. Повторный вызов с тем же ключом в течение AVITO_MCP_IDEMPOTENCY_TTL_SEC возвращает закешированный результат. Тот же ключ с другими args вернёт ошибку conflict — это безопасно по дизайну."New value: +"v0.7.0: optional key for duplicate protection. A repeat call with the same key within AVITO_MCP_IDEMPOTENCY_TTL_SEC returns the cached result. The same key with different args returns a conflict error — this is safe by design."
    • changedInput schema / properties / reason / description
      Previous value: -"Причина отмены."New value: +"Cancellation reason (optional)."
  5. First observedv0.7.4

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already signal destructiveness; description adds emphasis on irreversibility and reveals authorization behavior (403/404 for regular sellers). No contradiction with annotations, but could detail more side effects.

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 sentences are front-loaded with purpose, then key traits (irreversibility, prerequisite creator, authorization). No redundant words.

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?

No output schema is provided, and description does not explain return values or error states beyond the 403/404. It also lacks guidance on optional parameters (e.g., dryRun, idempotencyKey) and prerequisites beyond existence of announcement.

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%, with each parameter already described in detail. Description adds no additional parameter-level information, so baseline score of 3 is appropriate.

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?

Description clearly states the action (cancel) and resource (announcement), explicitly ties to 3PL-specific creation tool, and distinguishes from siblings by noting its exclusive use for 3PL accounts and the 403/404 response for regular sellers.

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?

Description indicates usage context (cancelling a previously created announcement) and implicitly restricts to 3PL accounts via error mention, but does not explicitly compare with sibling cancel tools or state when NOT to use it.

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

Deploy Server

Other Tools