Avito MCP

Overview Schema Source Related Servers Discussions Admin

Delivery: create announcement [3PL]

delivery_create_announcement_3pl

Creates a 3PL shipment announcement to notify the receiving delivery service about an upcoming parcel handover between sorting centers.

Instructions

[3PL] Creates an announcement of a planned shipment from one delivery service (sender) to another (receiver). The method is implemented on the delivery-service side — on a regular seller account it returns 403/404. Use it when you need to notify the receiving party about an upcoming parcel handover; unlike delivery_create_parcel this is a shipment announcement, not the creation of the parcel itself.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	Announcement creation date and time in 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 party and sorting center.
`barcode`	Yes	Unique announcement barcode, printed on the acceptance/handover act. Example: 000987654321.
`packages`	Yes	List of cargo units (at least one).
`receiver`	Yes	Receiving party and sorting center.
`announcementID`	Yes	Announcement identifier (required).
`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

Changed27 schema fields changedv1.2.0Jul 10, 2026

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 / announcementType / description

Previous value: -"Announcement type. Enum: DELIVERY (delivery) | PICKUP (pickup)."New value: +"Announcement type."

addedInput schema / properties / announcementType / enum
```
Added value: +[
+  "DELIVERY",
+  "PICKUP"
+]
```
removedInput schema / properties / date / additionalProperties
```
Removed value: -{}
```
addedInput schema / properties / date / minLength
```
Added value: +1
```
removedInput schema / properties / date / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

changedInput schema / properties / date / 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."

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"
+  },
+  "parcels": {
+    "items": {
+      "properties": {
+        "barcode": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "id": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "senderBarcode": {
+          "type": "string"
+        },
+        "senderID": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "barcode",
+        "id"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "sealID": {
+    "type": "string"
+  }
+}

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

changedInput schema / properties / receiver / description

Previous value: -"Receiving party: type (3PL), name, phones, email, delivery node/sorting center."New value: +"Receiving party and sorting center."

addedInput schema / properties / receiver / properties

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

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

addedInput schema / properties / receiver / required

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

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

changedInput schema / properties / sender / description

Previous value: -"Sending party: type (3PL), name, phones, email, delivery node/sorting center."New value: +"Sending party and sorting center."

addedInput schema / properties / sender / properties

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

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

addedInput schema / properties / sender / required

Added value: +[
+  "delivery",
+  "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"

Changed10 schema fields changedv0.8.0May 31, 2026

changedInput schema / properties / announcementID / description

Previous value: -"См. AnnouncementID в swaggers/Доставка.json"New value: +"Announcement identifier (required)."

changedInput schema / properties / announcementType / description

Previous value: -"Тип анонса."New value: +"Announcement type. Enum: DELIVERY (delivery) | PICKUP (pickup)."

changedInput schema / properties / barcode / description

Previous value: -"Штрихкод посылки."New value: +"Unique announcement barcode, printed on the acceptance/handover act. Example: 000987654321."

changedInput schema / properties / date / description

Previous value: -"См. Date в swaggers/Доставка.json"New value: +"Announcement creation date and time in 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 / packages / description

Previous value: -"Массив пакетов."New value: +"List of cargo units (at least one)."

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 party: type (3PL), name, phones, email, delivery node/sorting center."

changedInput schema / properties / sender / description

Previous value: -"См. Sender в swaggers/Доставка.json"New value: +"Sending party: type (3PL), name, phones, email, delivery node/sorting center."

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?

Annotations already indicate non-read-only, non-destructive, open-world, non-idempotent. The description adds that the tool is for 3PL accounts and returns 403/404 otherwise, which is important behavioral context. It also clarifies this is an announcement, not a parcel, distinguishing 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?

The description is concise (two sentences) with the most critical information front-loaded: purpose, applicability, and distinction from sibling. No extraneous text.

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 9 parameters with nested objects and no output schema, the description provides sufficient context about the tool's purpose, authorization constraints, and relationship to sibling tools. It lacks return value details but that is not required without output schema.

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 each parameter. The description does not add additional meaning beyond what the schema provides. For example, it mentions barcode and packages but the schema already describes them. Baseline 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 an announcement of a planned shipment between delivery services, specifies it is for 3PL accounts, and distinguishes it from delivery_create_parcel by noting this is a shipment announcement, not parcel creation. The verb 'creates' and resource 'announcement' are specific.

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?

The description explicitly states when to use ('notify the receiving party about an upcoming parcel handover') and what not to use (unlike delivery_create_parcel for parcel creation). It also notes the tool is for delivery-service side and returns 403/404 on regular seller accounts, providing clear usage context.

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 [3PL]

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools