Skip to main content
Glama
elchin92

Avito MCP

by elchin92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delivery: push tracking event [sandbox]

delivery_tracking

Append a parcel tracking event to Avito for delivery-service partners. Report movement as it happens; one call records one status transition in the parcel history.

Instructions

[SANDBOX] Appends one parcel tracking event to Avito on behalf of the delivery service; does not modify existing history — a single status transition (e.g. RECEIVED_AT_TRANSIT_TERMINAL → IN_TRANSIT). Use this to report movement as it happens; one call records one event, and events accumulate into the parcel history (not idempotent — re-sending logs a duplicate). Returns an empty 200 on success; a 4xx means the order/status pair was rejected. Comply with Avito's retry policy on 5xx. For delivery-service PARTNERS only (not regular sellers). Sibling tools: delivery_set_order_properties sets cost/parameters, delivery_change_parcels reschedules a parcel — this one only appends a status event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesEvent date and time in RFC 3339 format, UTC.
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).
commentNoComment on the status (optional).
optionsNoAdditional status options: parcel barcode, return numbers (optional).
orderIdYesOrder identifier.
locationYesEvent locality in the nominative case. Example: Kazan.
avitoStatusYesParcel status. Enum: CONFIRMED | IN_TRANSIT | ON_DELIVERY | DELIVERED | IN_TRANSIT_RETURN | ON_DELIVERY_RETURN | RETURNED | LOST | DESTROYED.
avitoEventTypeYesEvent code on the Avito side. Example: RECEIVED_AT_TRANSIT_TERMINAL.
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.
providerEventCodeYesEvent code as defined by the delivery service.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.3
  2. Removedv1.3.2
  3. Changed16 schema fields changedv1.2.0
    • removedInput schema / properties / avitoStatus / additionalProperties
      Removed value: -{}
    • addedInput schema / properties / avitoStatus / enum
      Added value: +[
+  "CONFIRMED",
+  "IN_TRANSIT",
+  "ON_DELIVERY",
+  "DELIVERED",
+  "IN_TRANSIT_RETURN",
+  "ON_DELIVERY_RETURN",
+  "RETURNED",
+  "LOST",
+  "DESTROYED"
+]
    • removedInput schema / properties / avitoStatus / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • changedInput schema / properties / avitoStatus / type
      Previous value: -"object"New value: +"string"
    • 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 / options / additionalProperties
      Removed value: -{}
    • addedInput schema / properties / options / properties
      Added value: +{
+  "barcode": {
+    "type": "string"
+  },
+  "returnBarcode": {
+    "type": "string"
+  },
+  "returnDispatchNumber": {
+    "type": "string"
+  },
+  "returnTrackingNumber": {
+    "type": "string"
+  }
+}
    • removedInput schema / properties / options / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / orderId / additionalProperties
      Removed value: -{}
    • addedInput schema / properties / orderId / minLength
      Added value: +1
    • removedInput schema / properties / orderId / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • changedInput schema / properties / orderId / type
      Previous value: -"object"New value: +"string"
  4. Changed2 schema fields changedv0.8.1
    • addedInput schema / properties / dryRun
      Added value: +{
+  "description": "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).",
+  "type": "boolean"
+}
    • addedInput schema / properties / idempotencyKey
      Added value: +{
+  "description": "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.",
+  "minLength": 8,
+  "type": "string"
+}
  5. Changed8 schema fields changedv0.8.0
    • changedInput schema / properties / avitoEventType / description
      Previous value: -"Тип события (см. swagger)."New value: +"Event code on the Avito side. Example: RECEIVED_AT_TRANSIT_TERMINAL."
    • changedInput schema / properties / avitoStatus / description
      Previous value: -"См. AvitoStatus в swaggers/Доставка.json"New value: +"Parcel status. Enum: CONFIRMED | IN_TRANSIT | ON_DELIVERY | DELIVERED | IN_TRANSIT_RETURN | ON_DELIVERY_RETURN | RETURNED | LOST | DESTROYED."
    • changedInput schema / properties / comment / description
      Previous value: -"Комментарий."New value: +"Comment on the status (optional)."
    • changedInput schema / properties / date / description
      Previous value: -"См. Date в swaggers/Доставка.json"New value: +"Event date and time in RFC 3339 format, UTC."
    • changedInput schema / properties / location / description
      Previous value: -"Локация события."New value: +"Event locality in the nominative case. Example: Kazan."
    • changedInput schema / properties / options / description
      Previous value: -"Опции."New value: +"Additional status options: parcel barcode, return numbers (optional)."
    • changedInput schema / properties / orderId / description
      Previous value: -"См. OrderID в swaggers/Доставка.json"New value: +"Order identifier."
    • changedInput schema / properties / providerEventCode / description
      Previous value: -"Код события у провайдера."New value: +"Event code as defined by the delivery service."
  6. First observedv0.7.4

TDQS

A4.5/5.0
Behavior5/5

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

The description goes beyond annotations by explaining that it does not modify existing history, is not idempotent (duplicate logging), returns empty 200 on success, and provides error semantics. It also mentions retry policy and audience. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at about 4-5 sentences and front-loads the purpose. Every sentence adds value, though it could be slightly more structured with bullet points.

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 10 parameters, no output schema, and annotations, the description covers usage, error handling, audience, and retry policy. It lacks explanation of the response beyond empty 200, but that is acceptable for a mutation 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% so the description does not need to repeat parameter details. It adds context by mentioning the event type and status transition as an example, but does not significantly augment the schema descriptions.

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 verb 'appends', the resource 'parcel tracking event', and scopes it to a single status transition. It distinguishes from siblings by specifying that this tool only appends status events, while others set cost/parameters or reschedule parcels.

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 says when to use ('report movement as it happens'), cautions about non-idempotency and duplicate logging, explains error responses (4xx rejection, 5xx retry), and limits usage to delivery-service PARTNERS. It also names sibling tools and their purposes.

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