Skip to main content
Glama
elchin92

Avito MCP

by elchin92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

⚠️ CPA auction: save bids

cpa_auction_save_item_bids
Destructive

Save or overwrite CPA auction bids for up to 200 Avito listings, specifying cost per action in kopecks and optional expiration time to control visibility and advertising spend.

Instructions

Saves (overwrites) CPA auction bids for listings. WARNING: affects auction spending (money) — a higher bid means a higher display position. pricePenny is in kopecks per action; expirationTime sets the validity period (omitted or null — indefinite). Up to 200 listings per request, limit 200 requests/min. For current and available bids see cpa_auction_get_user_bids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesArray of bids (1–200). Each element: itemID (int, listing ID, required), pricePenny (int, bid in kopecks, required), expirationTime (string RFC3339, e.g. "2023-06-29T12:34:34+03:00"; null/absent — indefinite). See swaggers/cpa-auction.json.
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).
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. Changed5 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 / items / items / additionalProperties
      Removed value: -{}
    • addedInput schema / properties / items / items / properties
      Added value: +{
+  "expirationTime": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "itemID": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "pricePenny": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  }
+}
    • removedInput schema / properties / items / items / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / items / items / required
      Added value: +[
+  "itemID",
+  "pricePenny"
+]
  2. Changed1 schema field changedv0.8.1
    • changedInput schema / properties / items / description
      Previous value: -"Array of bids (1–200). Each element: itemID (int, listing ID, required), pricePenny (int, bid in kopecks, required), expirationTime (string RFC3339, e.g. \"2023-06-29T12:34:34+03:00\"; null/absent — indefinite). See swaggers/CPA-аукцион.json."New value: +"Array of bids (1–200). Each element: itemID (int, listing ID, required), pricePenny (int, bid in kopecks, required), expirationTime (string RFC3339, e.g. \"2023-06-29T12:34:34+03:00\"; null/absent — indefinite). See swaggers/cpa-auction.json."
  3. Changed3 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 / 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 / items / description
      Previous value: -"Массив ставок {itemId, bid, ...}. См. swaggers/CPA-аукцион.json."New value: +"Array of bids (1–200). Each element: itemID (int, listing ID, required), pricePenny (int, bid in kopecks, required), expirationTime (string RFC3339, e.g. \"2023-06-29T12:34:34+03:00\"; null/absent — indefinite). See swaggers/CPA-аукцион.json."
  4. First observedv0.7.4

TDQS

A4.4/5.0
Behavior4/5

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

The description adds valuable behavioral context beyond annotations: it warns about financial impact ('affects auction spending (money)'), clarifies the meaning of pricePenny and expirationTime, and notes the limits. No contradiction with annotations (destructiveHint=true). Annotations already mark as destructive and non-idempotent; description reinforces and elaborates.

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 very concise: three sentences covering purpose, warning, parameter details, limits, and cross-reference. No unnecessary words. Front-loaded with the core action.

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?

The description covers purpose, financial implications, parameter semantics, limits, and where to find current bids. Missing only what the tool returns (no output schema), but this is partially compensated by the clear mutation nature and the sibling reference.

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%, so baseline is 3. The description adds meaning beyond the schema: it explains pricePenny is 'in kopecks per action' and expirationTime 'omitted or null — indefinite', and states the array limit and request rate limit. This provides practical usage guidance.

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 uses the strong verb 'saves (overwrites)' and clearly specifies the resource (CPA auction bids for listings). It distinguishes from the sibling tool cpa_auction_get_user_bids, which is for viewing bids.

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 provides clear context: it overwrites bids, affects spending, and includes limits (200 listings, 200 req/min). It also directs users to the sibling tool for current bids. However, it does not explicitly state when not to use this tool (e.g., for read-only 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