Skip to main content
Glama
elchin92

Avito MCP

by elchin92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delivery: cancel announcement [sandbox v1]

delivery_v1_cancel_announcement
Destructive

Cancel a test announcement in the Avito Sandbox for delivery-service partners via the v1 API, providing announcement ID, date, and callback URL.

Instructions

[SANDBOX v1] Starts the process of cancelling a test announcement; on success the response has a success status. Available only in the Sandbox, for delivery-service partners. Unlike delivery_cancel_announcement_3pl (production /cancelAnnouncement), this is the test v1 contract with a required options field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesEvent date and time in ISO 8601 (RFC 3339) format.
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).
optionsYesCallback URL used to cancel the announcement.
announcementIDYesIdentifier of the test announcement to cancel.
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. Changed6 schema fields changedv1.2.0
    • 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."
    • removedInput schema / properties / options / additionalProperties
      Removed value: -{}
    • changedInput schema / properties / options / description
      Previous value: -"Additional announcement-cancellation options."New value: +"Callback URL used to cancel the announcement."
    • addedInput schema / properties / options / properties
      Added value: +{
+  "urlToCancelAnnouncement": {
+    "minLength": 1,
+    "type": "string"
+  }
+}
    • removedInput schema / properties / options / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / options / required
      Added value: +[
+  "urlToCancelAnnouncement"
+]
  2. Changed5 schema fields changedv0.8.0
    • addedInput schema / properties / announcementID / description
      Added value: +"Identifier of the test announcement to cancel."
    • changedInput schema / properties / date / description
      Previous value: -"Дата (ISO 8601)."New value: +"Event date and time in ISO 8601 (RFC 3339) format."
    • 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 / options / description
      Previous value: -"См. Options в swaggers/Доставка.json"New value: +"Additional announcement-cancellation options."
  3. First observedv0.7.4

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. Description adds minor context: 'starts the process' implying potential async behavior, and 'on success the response has a success status' (obvious). No additional behavioral traits disclosed beyond what annotations provide.

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?

Two sentences are concise and front-load the key information (sandbox, cancellation, success status). Minor redundancy with '[SANDBOX v1]' prefix could be integrated better, but overall efficient.

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?

With no output schema, the description should give more detail on return values beyond 'success status'. Also lacks guidance on error cases or side effects. Given the tool's simplicity and 5 parameters, the description is minimally adequate but has clear gaps.

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 has 100% coverage of parameter descriptions, including the nested options object. The description only mentions 'required options field' without adding meaning beyond the schema. Baseline 3 is appropriate as schema does the heavy lifting.

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?

The description clearly states it cancels a test announcement in the sandbox, using specific verb 'cancelling' and resource 'test announcement'. It distinguishes from sibling tool delivery_cancel_announcement_3pl by noting sandbox vs production and different contract versions.

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?

Explicitly states availability only in Sandbox for delivery-service partners and contrasts with the production alternative. However, it does not provide explicit when-not-to-use scenarios beyond the environment restriction.

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