Avito MCP

Overview Schema Source Related Servers Discussions Admin

Delivery: upload pickup points [sandbox]

delivery_add_terminals_sandbox

Destructive

Upload and replace the full set of pickup points and parcel lockers for a delivery tariff. Changes are auto-approved unless critical, then queued for manual review.

Instructions

Replaces the tariff's terminal set. [SANDBOX] Uploads terminals (pickup points / parcel lockers) for one tariff. Auto-approves on accept (200); when a high share of the changes are critical the upload is queued for manual review instead. For delivery-service PARTNERS only. The request body is the terminals array directly (the tool wraps it for you).

Input Schema

TableJSON Schema

Name	Required	Description
`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).
`tariff_id`	Yes	Tariff identifier (int32, in path); legacy decimal strings remain accepted.
`terminals`	Yes	Array of pickup points: deliveryProviderId, name, address, phones, services (intake/delivery), schedule, type (PVZ\|POSTAMAT, default PVZ).
`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

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

addedInput schema / properties / tariff_id / anyOf

Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^-?\\d+$",
+    "type": "string"
+  }
+]

changedInput schema / properties / tariff_id / description

Previous value: -"Tariff identifier (in path)."New value: +"Tariff identifier (int32, in path); legacy decimal strings remain accepted."

removedInput schema / properties / tariff_id / type
```
Removed value: -"string"
```
removedInput schema / properties / terminals / items / additionalProperties
```
Removed value: -{}
```
removedInput schema / properties / terminals / items / description
```
Removed value: -"See Terminal in swaggers/delivery.json"
```

addedInput schema / properties / terminals / items / properties

Added value: +{
+  "address": {
+    "properties": {
+      "addressRow": {
+        "type": "string"
+      },
+      "building": {
+        "type": "string"
+      },
+      "country": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "fias": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "floor": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "house": {
+        "type": "string"
+      },
+      "housing": {
+        "type": "string"
+      },
+      "lat": {
+        "maximum": 81.8,
+        "minimum": 41.1,
+        "type": "number"
+      },
+      "lng": {
+        "maximum": 180,
+        "minimum": -180,
+        "type": "number"
+      },
+      "locality": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "localityType": {
+        "type": "string"
+      },
+      "porch": {
+        "type": "string"
+      },
+      "region": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "room": {
+        "type": "string"
+      },
+      "street": {
+        "type": "string"
+      },
+      "subRegion": {
+        "type": "string"
+      },
+      "subRegionType": {
+        "type": "string"
+      },
+      "zipCode": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "country",
+      "fias",
+      "lat",
+      "lng",
+      "locality",
+      "region",
+      "zipCode"
+    ],
+    "type": "object"
+  },
+  "deliveryProviderId": {
+    "maxLength": 64,
+    "type": "string"
+  },
+  "directionTag": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "displayName": {
+    "type": "string"
+  },
+  "itinerary": {
+    "type": "string"
+  },
+  "name": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "options": {
+    "items": {
+      "enum": [
+        "fitting",
+        "electronics-checking",
+        "cod-by-card",
+        "cod-by-cash",
+        "multi-drop-off"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "phones": {
+    "items": {
+      "pattern": "^7[0-9]{10}$",
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "photos": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "restriction": {
+    "properties": {
+      "dimensionalFactor": {
+        "maximum": 100000,
+        "minimum": 1000,
+        "type": "integer"
+      },
+      "maxDeclaredCost": {
+        "maximum": 15000000,
+        "minimum": 1000,
+        "type": "integer"
+      },
+      "maxDimensionalWeight": {
+        "maximum": 100000000000,
+        "minimum": 1000,
+        "type": "integer"
+      },
+      "maxDimensions": {
+        "items": {
+          "maximum": 3000,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "type": "array"
+      },
+      "maxWeight": {
+        "maximum": 100000000000,
+        "minimum": 1000,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "maxDeclaredCost",
+      "maxDimensions",
+      "maxWeight"
+    ],
+    "type": "object"
+  },
+  "schedule": {
+    "properties": {
+      "fri": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "mon": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "sat": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "sun": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "thu": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "tue": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "wed": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "mon",
+      "tue",
+      "wed",
+      "thu",
+      "fri",
+      "sat",
+      "sun"
+    ],
+    "type": "object"
+  },
+  "services": {
+    "items": {
+      "enum": [
+        "intake",
+        "delivery"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "type": {
+    "enum": [
+      "PVZ",
+      "POSTAMAT"
+    ],
+    "type": "string"
+  }
+}

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

addedInput schema / properties / terminals / items / required

Added value: +[
+  "address",
+  "deliveryProviderId",
+  "directionTag",
+  "itinerary",
+  "name",
+  "phones",
+  "photos",
+  "restriction",
+  "schedule",
+  "services"
+]

Changed1 schema field changedv0.8.1Jun 17, 2026

changedInput schema / properties / terminals / items / description

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

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

changedInput schema / properties / tariff_id / description

Previous value: -"ID тарифа."New value: +"Tariff identifier (in path)."

changedInput schema / properties / terminals / description

Previous value: -"Массив терминалов."New value: +"Array of pickup points: deliveryProviderId, name, address, phones, services (intake/delivery), schedule, type (PVZ|POSTAMAT, default PVZ)."

changedInput schema / properties / terminals / items / description

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

First observedv0.7.4May 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already indicate destructive and non-idempotent behavior. The description adds valuable context: 'Replaces the tariff's terminal set' (destructive), the auto-approval vs. manual review process, and partner-only restriction. No contradictions with annotations.

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 with no wasted words. The description is front-loaded with the primary action, includes the [SANDBOX] tag, and provides essential behavioral details efficiently.

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?

While input schema coverage is 100% and annotations are present, the description lacks information about the response format or error cases. For a tool that replaces a terminal set, an agent would benefit from knowing what the 200 response contains or what triggers manual review.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds the crucial hint that the request body is the terminals array directly (the tool wraps it). This clarifies that the main payload is the terminals parameter, adding meaning beyond the schema.

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 replaces the tariff's terminal set by uploading terminals (pickup points/parcel lockers). The verb 'replaces' and resource 'terminals for a tariff' are specific, and it distinguishes from sibling tools like delivery_add_areas_sandbox which deal with areas, not terminals.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description specifies it is for 'delivery-service PARTNERS only' and explains auto-approval vs. manual review. However, it does not explicitly state when not to use this tool or suggest alternatives among the many delivery siblings, leaving usage guidance incomplete.

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

Deploy Server

Delivery: upload pickup points [sandbox]

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools