Skip to main content
Glama
elchin92

Avito MCP

by elchin92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delivery: parcel change result

delivery_change_parcel_result

Send Avito the parcel change outcome: approved or declined.

Instructions

[3PL] Sends Avito the outcome of a parcel change request previously sent via delivery_change_parcels: the delivery service reports whether the request was approved (approved) or rejected (declined). A production method on the delivery-service side — on a regular seller account it returns 403/404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesIdentifier of the parcel change request.
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).
reasonNoRejection reason; filled in when status=declined (optional).
statusYesRequest processing status.
optionsNoAdditional result options (optional).
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.3
  2. Removedv1.3.2
  3. Changed7 schema fields changedv1.2.0
    • 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 / anyOf
      Added value: +[
+  {
+    "properties": {
+      "storageExtendedTo": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / options / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / options / type
      Removed value: -"object"
    • changedInput schema / properties / status / description
      Previous value: -"Request processing status. Enum: approved | declined."New value: +"Request processing status."
    • addedInput schema / properties / status / enum
      Added value: +[
+  "approved",
+  "declined"
+]
  4. Changed6 schema fields changedv0.8.0
    • 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 / id / description
      Previous value: -"ID заявки."New value: +"Identifier of the parcel change request."
    • 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 result options (optional)."
    • changedInput schema / properties / reason / description
      Previous value: -"Причина."New value: +"Rejection reason; filled in when status=declined (optional)."
    • changedInput schema / properties / status / description
      Previous value: -"Статус результата."New value: +"Request processing status. Enum: approved | declined."
  5. First observedv0.7.4

TDQS

A3.8/5.0
Behavior3/5

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

Annotations indicate write operation (readOnlyHint=false) and non-idempotent. The description adds that it sends the outcome and includes an edge case (403/404 on regular accounts). However, it does not explain potential side effects or state changes beyond the basic operation.

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 a single sentence with a brief note about production behavior. It is concise, front-loaded with the main action, and contains no unnecessary information.

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 the tool's simplicity and no output schema, the description adequately covers the purpose, result statuses, and a key behavioral note. It could briefly mention the 'options' parameter's role but is sufficient overall.

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 each parameter already has a description. The tool description does not add significant new meaning beyond the schema, meeting the baseline expectation.

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 sends the outcome of a parcel change request (approved/declined) to Avito, referring to the related tool delivery_change_parcels. It distinguishes itself as the follow-up result reporting tool.

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 mentions that this is for 3PL and that on regular seller accounts it returns 403/404, but does not explicitly state when to use this tool versus alternatives or when not to use it. The reference to delivery_change_parcels helps but lacks explicit exclusions.

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