Avito MCP

Overview Schema Source Related Servers Discussions Admin

Delivery: create parcel [sandbox]

delivery_create_sandbox_parcel_v2

Create a sandbox test parcel to get its parcelID, so you can test the full delivery lifecycle without affecting real-world data.

Instructions

[SANDBOX v2] Creates a test parcel in the Sandbox (no real-world effect) and returns its parcelID — the entry point for the sandbox parcel lifecycle: feed that id into delivery_v1_get_parcel_info, delivery_v1_get_registered_parcel_id, delivery_v1_change_parcel and delivery_v1_cancel_parcel. Unlike delivery_create_parcel ([3PL] production creation), this has no consequences. For delivery-service PARTNERS testing only.

Input Schema

TableJSON Schema

Name	Required	Description
`tags`	No	Test-parcel tags for Sandbox scenarios (optional).
`items`	No	Parcel contents (optional).
`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`	No	Sender and departure terminal (optional).
`options`	No	Additional test-parcel options (optional).
`receiver`	No	Receiver delivery options (optional).
`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.

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed18 schema fields changedv1.2.0Jul 10, 2026

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

changedInput schema / properties / items / description

Previous value: -"Parcel contents — items (optional)."New value: +"Parcel contents (optional)."

removedInput schema / properties / items / items / additionalProperties
```
Removed value: -{}
```
removedInput schema / properties / items / items / description
```
Removed value: -"See Item in swaggers/delivery.json"
```

addedInput schema / properties / items / items / properties

Added value: +{
+  "breadcrumbs": {
+    "items": {
+      "properties": {
+        "name": {
+          "maxLength": 255,
+          "type": "string"
+        }
+      },
+      "required": [
+        "name"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "cost": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "description": {
+    "type": "string"
+  },
+  "dimensions": {
+    "properties": {
+      "values": {
+        "items": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "maxItems": 3,
+        "minItems": 3,
+        "type": "array"
+      }
+    },
+    "type": "object"
+  },
+  "quantity": {
+    "maximum": 10,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "tags": {
+    "items": {
+      "const": "TRY_ON",
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "title": {
+    "type": "string"
+  },
+  "weight": {
+    "properties": {
+      "value": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  }
+}

removedInput schema / properties / items / items / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
addedInput schema / properties / items / items / required
```
Added value: +[
+  "quantity"
+]
```
removedInput schema / properties / options / additionalProperties
```
Removed value: -{}
```

addedInput schema / properties / options / properties

Added value: +{
+  "registrationUrl": {
+    "type": "string"
+  }
+}

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

changedInput schema / properties / receiver / description

Previous value: -"Receiver: full name, phone, address/pickup-point code (optional)."New value: +"Receiver delivery options (optional)."

addedInput schema / properties / receiver / properties

Added value: +{
+  "delivery": {
+    "properties": {
+      "courier": {
+        "properties": {
+          "address": {
+            "properties": {
+              "addressRow": {
+                "type": "string"
+              },
+              "coordinates": {
+                "properties": {
+                  "latitude": {
+                    "maximum": 90,
+                    "minimum": -90,
+                    "type": "number"
+                  },
+                  "longitude": {
+                    "maximum": 180,
+                    "minimum": -180,
+                    "type": "number"
+                  }
+                },
+                "required": [
+                  "latitude",
+                  "longitude"
+                ],
+                "type": "object"
+              },
+              "details": {
+                "properties": {
+                  "flat": {
+                    "type": "string"
+                  },
+                  "floor": {
+                    "type": "string"
+                  },
+                  "house": {
+                    "type": "string"
+                  },
+                  "porch": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "flat",
+                  "floor",
+                  "house",
+                  "porch"
+                ],
+                "type": "object"
+              }
+            },
+            "required": [
+              "addressRow",
+              "coordinates",
+              "details"
+            ],
+            "type": "object"
+          },
+          "dateTimeInterval": {
+            "properties": {
+              "end": {
+                "minLength": 1,
+                "type": "string"
+              },
+              "start": {
+                "minLength": 1,
+                "type": "string"
+              }
+            },
+            "required": [
+              "end",
+              "start"
+            ],
+            "type": "object"
+          },
+          "options": {
+            "properties": {
+              "comment": {
+                "type": "string"
+              },
+              "elevatorAvailable": {
+                "type": "boolean"
+              }
+            },
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "terminal": {
+        "properties": {
+          "id": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      }
+    },
+    "type": "object"
+  }
+}

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

changedInput schema / properties / sender / description

Previous value: -"Sender: details and sending node (optional)."New value: +"Sender and departure terminal (optional)."

addedInput schema / properties / sender / properties

Added value: +{
+  "delivery": {
+    "properties": {
+      "terminal": {
+        "properties": {
+          "id": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      }
+    },
+    "type": "object"
+  },
+  "inn": {
+    "type": "string"
+  }
+}

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

Changed1 schema field changedv0.8.1Jun 17, 2026

changedInput schema / properties / items / items / description

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

Changed8 schema fields changedv0.8.0May 31, 2026

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

addedInput schema / properties / items / description

Added value: +"Parcel contents — items (optional)."

changedInput schema / properties / items / items / description

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

changedInput schema / properties / options / description

Previous value: -"См. Options в swaggers/Доставка.json"New value: +"Additional test-parcel options (optional)."

changedInput schema / properties / receiver / description

Previous value: -"См. Receiver в swaggers/Доставка.json"New value: +"Receiver: full name, phone, address/pickup-point code (optional)."

changedInput schema / properties / sender / description

Previous value: -"См. Sender в swaggers/Доставка.json"New value: +"Sender: details and sending node (optional)."

addedInput schema / properties / tags / description

Added value: +"Test-parcel tags for Sandbox scenarios (optional)."

First observedv0.7.4May 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Disclosures include no real-world effect, no consequences, and return of parcelID. Aligns with annotations (readOnlyHint=false implies write operation, destructiveHint=false supports no consequences).

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?

Concise two-sentence structure: first sentence defines purpose and return, second provides comparison and usage context. No redundant information.

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

Completeness5/5

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

Given complexity (7 optional parameters, nested objects, no output schema), the description covers sandbox scope, lifecycle, target audience, and key return value fully. Enough for agent to decide and invoke.

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 parameter descriptions. The tool description does not add significant parameter-specific detail but provides context about the sandbox lifecycle and return value.

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 the tool creates a test parcel in the Sandbox with no real-world effect, returns parcelID, and distinguishes it from the production sibling delivery_create_parcel.

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?

Explicitly states 'For delivery-service PARTNERS testing only', contrasts with production creation, and identifies it as the entry point for a sandbox lifecycle with links to subsequent tools.

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 parcel [sandbox]

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools