Avito MCP

Overview Schema Source Related Servers Discussions Admin

Autoload: save profile

autoload_create_or_update_profile_v2

Destructive

Upsert an autoload profile with multiple feeds and a scheduled upload plan. Configure enabling, report email, and feed URLs; overwrites existing settings or creates a new profile.

Instructions

Creates or updates (upsert) an autoload profile (v2, current version). Overwrites the existing profile settings on the Avito side; if no profile exists, it creates one. Supports multiple feeds via feeds_data (unlike v1 with a single upload_url) — prefer this method. The uploads themselves run on the schedule, or manually via autoload_upload.

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).
`schedule`	Yes	Schedule of regular uploads (array of periods): each element = {rate: number of listings per period, weekdays: [0-6, where 0=Monday], time_slots: [0-23, where 0 = the 00:00-01:00 interval]}. Moscow time. Required. See the ExportSchedule schema in swagger autoload.json.
`agreement`	No	Acceptance of the Avito Autoload terms of use. Required only when first creating a profile; can be omitted on update.
`feeds_data`	Yes	Array of feeds (at least one). Each element = {feed_name: feed name for the report, feed_url: URL of the file with listings, starts with http/https}. Required. See the FeedsData schema in swagger autoload.json.
`report_email`	Yes	Email address to which Avito will send upload reports. 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.
`autoload_enabled`	Yes	Autoload status: true — enabled, false — disabled. Required.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv1.2.0Jul 10, 2026

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

addedInput schema / properties / feeds_data / items / properties

Added value: +{
+  "feed_name": {
+    "type": "string"
+  },
+  "feed_url": {
+    "format": "uri",
+    "type": "string"
+  }
+}

removedInput schema / properties / feeds_data / items / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
addedInput schema / properties / feeds_data / items / required
```
Added value: +[
+  "feed_name",
+  "feed_url"
+]
```

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 / schedule / additionalProperties
```
Removed value: -{}
```

addedInput schema / properties / schedule / items

Added value: +{
+  "properties": {
+    "rate": {
+      "description": "Number of listings to upload during this period.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "time_slots": {
+      "description": "Hourly Moscow-time slots from 0 through 23.",
+      "items": {
+        "maximum": 23,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    "weekdays": {
+      "description": "Weekdays from 0 (Monday) through 6 (Sunday).",
+      "items": {
+        "maximum": 6,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "rate",
+    "weekdays",
+    "time_slots"
+  ],
+  "type": "object"
+}

removedInput schema / properties / schedule / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
changedInput schema / properties / schedule / type
```
Previous value: -"object"New value: +"array"
```

Changed2 schema fields changedv0.8.1Jun 17, 2026

changedInput schema / properties / feeds_data / description

Previous value: -"Array of feeds (at least one). Each element = {feed_name: feed name for the report, feed_url: URL of the file with listings, starts with http/https}. Required. See the FeedsData schema in swagger Автозагрузка.json."New value: +"Array of feeds (at least one). Each element = {feed_name: feed name for the report, feed_url: URL of the file with listings, starts with http/https}. Required. See the FeedsData schema in swagger autoload.json."

changedInput schema / properties / schedule / description

Previous value: -"Schedule of regular uploads (array of periods): each element = {rate: number of listings per period, weekdays: [0-6, where 0=Monday], time_slots: [0-23, where 0 = the 00:00-01:00 interval]}. Moscow time. Required. See the ExportSchedule schema in swagger Автозагрузка.json."New value: +"Schedule of regular uploads (array of periods): each element = {rate: number of listings per period, weekdays: [0-6, where 0=Monday], time_slots: [0-23, where 0 = the 00:00-01:00 interval]}. Moscow time. Required. See the ExportSchedule schema in swagger autoload.json."

Changed7 schema fields changedv0.8.0May 31, 2026

changedInput schema / properties / agreement / description

Previous value: -"Принятие условий использования."New value: +"Acceptance of the Avito Autoload terms of use. Required only when first creating a profile; can be omitted on update."

changedInput schema / properties / autoload_enabled / description

Previous value: -"Включена ли автозагрузка."New value: +"Autoload status: true — enabled, false — disabled. Required."

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

Previous value: -"Массив фидов: {url, category_id, ...}. См. swagger Автозагрузка.json."New value: +"Array of feeds (at least one). Each element = {feed_name: feed name for the report, feed_url: URL of the file with listings, starts with http/https}. Required. See the FeedsData schema in swagger Автозагрузка.json."

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

Previous value: -"Email для отчётов автозагрузки."New value: +"Email address to which Avito will send upload reports. Required."

changedInput schema / properties / schedule / description

Previous value: -"Расписание выгрузок."New value: +"Schedule of regular uploads (array of periods): each element = {rate: number of listings per period, weekdays: [0-6, where 0=Monday], time_slots: [0-23, where 0 = the 00:00-01:00 interval]}. Moscow time. Required. See the ExportSchedule schema in swagger Автозагрузка.json."

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?

The description discloses the upsert behavior (overwrites or creates) and that it is destructive (annotation destructiveHint=true). It adds context about overwriting existing settings. Could mention behavior for unspecified fields, but sufficient given 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 pack essential information: core function, upsert and v2 advantage, and separation from uploads. No redundancy, front-loaded.

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?

Description covers key behavioral aspects for a complex tool with 7 params. Missing explicit mention of agreement parameter behavior, but schema provides that. Overall adequate.

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% with detailed parameter descriptions. The tool description adds value by highlighting dryRun's purpose and the multiple feeds advantage over v1, beyond schema alone.

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 or updates an autoload profile (upsert), specifies it is v2 (current), and distinguishes it from v1 by supporting multiple feeds. It also separates profile management from uploads, differentiating from autoload_upload.

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

Usage Guidelines4/5

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

The description advises preferring this method over v1 due to multiple feed support and notes that uploads are handled separately via autoload_upload. It lacks explicit exclusion scenarios but provides clear context on when to use the tool.

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

Deploy Server

Autoload: save profile

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools