Avito MCP

Overview Schema Source Related Servers Discussions Admin

Delivery: create announcement [sandbox v1]

delivery_v1_create_announcement

Create test shipment announcements in the Avito Sandbox for delivery partners, enabling safe validation of delivery workflows without real-world effects.

Instructions

[SANDBOX v1] Creates a test shipment announcement in the Sandbox (no real-world effect); returns a success status. Use the base contract delivery_sandbox_create_announcement unless you specifically need this v1 shape — the only difference is that v1 additionally requires the options field. Sandbox-only, for delivery-service PARTNERS.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	Announcement creation date and time in ISO 8601 (RFC 3339) format, UTC.
`dryRun`	No	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).
`sender`	Yes	Sending delivery service and delivery point.
`barcode`	Yes	Unique announcement barcode (printed on the acceptance/handover act).
`options`	Yes	Announcement callback options.
`packages`	Yes	List of cargo units.
`receiver`	Yes	Receiving delivery service and delivery point.
`announcementID`	Yes	Identifier of the announcement to create.
`idempotencyKey`	No	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.
`announcementType`	Yes	Announcement type.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.3.3Jul 29, 2026
Removedv1.3.2Jul 17, 2026

Changed23 schema fields changedv1.2.0Jul 10, 2026

changedInput schema / properties / announcementType / description

Previous value: -"Announcement type. Enum: DELIVERY | PICKUP."New value: +"Announcement type."

addedInput schema / properties / announcementType / enum
```
Added value: +[
+  "DELIVERY",
+  "PICKUP"
+]
```

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 options."New value: +"Announcement callback options."

addedInput schema / properties / options / properties

Added value: +{
+  "urlToSendAnnouncement": {
+    "minLength": 1,
+    "type": "string"
+  }
+}

removedInput schema / properties / options / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
addedInput schema / properties / options / required
```
Added value: +[
+  "urlToSendAnnouncement"
+]
```
removedInput schema / properties / packages / items / additionalProperties
```
Removed value: -{}
```
removedInput schema / properties / packages / items / description
```
Removed value: -"See Package in swaggers/delivery.json"
```

addedInput schema / properties / packages / items / properties

Added value: +{
+  "id": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "parcelIDs": {
+    "items": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "sealID": {
+    "type": "string"
+  }
+}

removedInput schema / properties / packages / items / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
addedInput schema / properties / packages / items / required
```
Added value: +[
+  "id",
+  "parcelIDs"
+]
```
removedInput schema / properties / receiver / additionalProperties
```
Removed value: -{}
```

changedInput schema / properties / receiver / description

Previous value: -"Receiving delivery service: type, name, phones, email, delivery node/sorting center."New value: +"Receiving delivery service and delivery point."

addedInput schema / properties / receiver / properties

Added value: +{
+  "delivery": {
+    "properties": {
+      "sortingCenter": {
+        "properties": {
+          "accuracy": {
+            "enum": [
+              "EXACT",
+              "APPROXIMATE"
+            ],
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "provider": {
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "provider"
+        ],
+        "type": "object"
+      },
+      "terminal": {
+        "properties": {
+          "accuracy": {
+            "enum": [
+              "EXACT",
+              "APPROXIMATE"
+            ],
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "provider": {
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "provider"
+        ],
+        "type": "object"
+      },
+      "type": {
+        "enum": [
+          "TERMINAL",
+          "SORTING_CENTER"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "type"
+    ],
+    "type": "object"
+  },
+  "email": {
+    "type": "string"
+  },
+  "name": {
+    "type": "string"
+  },
+  "phones": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "type": {
+    "enum": [
+      "3PL",
+      "ABD"
+    ],
+    "type": "string"
+  }
+}

removedInput schema / properties / receiver / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

addedInput schema / properties / receiver / required

Added value: +[
+  "delivery",
+  "email",
+  "name",
+  "phones",
+  "type"
+]

removedInput schema / properties / sender / additionalProperties
```
Removed value: -{}
```

changedInput schema / properties / sender / description

Previous value: -"Sending party: type, name, phones, email, sending node."New value: +"Sending delivery service and delivery point."

addedInput schema / properties / sender / properties

Added value: +{
+  "delivery": {
+    "properties": {
+      "sortingCenter": {
+        "properties": {
+          "accuracy": {
+            "enum": [
+              "EXACT",
+              "APPROXIMATE"
+            ],
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "provider": {
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "provider"
+        ],
+        "type": "object"
+      },
+      "terminal": {
+        "properties": {
+          "accuracy": {
+            "enum": [
+              "EXACT",
+              "APPROXIMATE"
+            ],
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "provider": {
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "provider"
+        ],
+        "type": "object"
+      },
+      "type": {
+        "enum": [
+          "TERMINAL",
+          "SORTING_CENTER"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "type"
+    ],
+    "type": "object"
+  },
+  "email": {
+    "type": "string"
+  },
+  "name": {
+    "type": "string"
+  },
+  "phones": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "type": {
+    "enum": [
+      "3PL",
+      "ABD"
+    ],
+    "type": "string"
+  }
+}

removedInput schema / properties / sender / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

addedInput schema / properties / sender / required

Added value: +[
+  "delivery",
+  "email",
+  "name",
+  "phones",
+  "type"
+]

Changed1 schema field changedv0.8.1Jun 17, 2026

changedInput schema / properties / packages / items / description

Previous value: -"See Package in swaggers/Доставка.json"New value: +"See Package in swaggers/delivery.json"

Changed11 schema fields changedv0.8.0May 31, 2026

addedInput schema / properties / announcementID / description
```
Added value: +"Identifier of the announcement to create."
```
addedInput schema / properties / announcementType / description
```
Added value: +"Announcement type. Enum: DELIVERY | PICKUP."
```

addedInput schema / properties / barcode / description

Added value: +"Unique announcement barcode (printed on the acceptance/handover act)."

changedInput schema / properties / date / description

Previous value: -"ISO 8601."New value: +"Announcement creation date and time in ISO 8601 (RFC 3339) format, UTC."

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 options."

addedInput schema / properties / packages / description
```
Added value: +"List of cargo units."
```

changedInput schema / properties / packages / items / description

Previous value: -"См. Package в swaggers/Доставка.json"New value: +"See Package in swaggers/Доставка.json"

changedInput schema / properties / receiver / description

Previous value: -"См. Receiver в swaggers/Доставка.json"New value: +"Receiving delivery service: type, name, phones, email, delivery node/sorting center."

changedInput schema / properties / sender / description

Previous value: -"См. Sender в swaggers/Доставка.json"New value: +"Sending party: type, name, phones, email, sending node."

First observedv0.7.4May 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Disclosures: sandbox-only, no real-world effect, returns success status. Annotations already indicate non-readOnly and non-destructive. Description adds context but could mention more about side effects or reversibility.

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?

Two concise sentences, front-loaded with purpose and scope. No waste; every sentence adds value.

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

Completeness4/5

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

Given complexity (10 params, nested) and no output schema, the description covers key context: sandbox, partnership, and sibling differentiation. Could elaborate on return value details but sufficient for a test tool.

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 descriptions for all parameters. The description adds minimal param info beyond the schema, only highlighting that v1 requires the options field. Baseline 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?

The description clearly states it creates a test shipment announcement in the Sandbox with no real-world effect. It distinguishes itself from the sibling tool delivery_sandbox_create_announcement by noting the v1 shape requires the options field.

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?

Explicit usage guidance: use the base contract unless v1 is specifically needed due to the options requirement. Also specifies sandbox-only and for delivery-service PARTNERS.

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

Deploy Server

Delivery: create announcement [sandbox v1]

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools