avito-mcp-ru

Overview Schema Source Related Servers Score Discussions Admin

avito_set_key

Idempotent

Rotate or replace the marketplace API key from chat when the old one expired or leaked; the key is validated against the marketplace and stored locally.

Instructions

Change / rotate the API key from chat (e.g. the old one expired or leaked).

⚠️ The key goes into the chat transcript — requires i_understand_key_goes_to_chat=true. The safe, terminal-free alternative is the installer, where the key never enters chat. Use a scoped key and rotate it in the seller cabinet if it was exposed.

Args: credentials: dict with the required fields ({fields}). cabinet: which cabinet to update. Default: the active one (so "my key expired" just works). If there is none, the cabinet is named from the marketplace's shop name, else "main". i_understand_key_goes_to_chat: must be true to proceed. On success the key is validated against the marketplace and the shop name is reported. Saved locally (chmod 600), never echoed back.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cabinet`	No
`credentials`	Yes
`i_understand_key_goes_to_chat`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.3Sep 11, 2026

TDQS

A5/5.0

Behavior5/5

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

Goes well beyond annotations: discloses that the key enters the chat transcript, requires an explicit acknowledgment flag, validates the key on success, saves locally with chmod 600, and never echoes it back. This adds significant context beyond the basic readOnly/destructive hints.

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 well-structured with a security warning up front, followed by concise parameter explanations. Every sentence adds value, and the length is justified by the sensitive nature of the operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers security implications, default behaviors, validation, and storage details. Given an output schema exists, the description provides all necessary information for correct invocation without redundant return-type explanation.

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

Parameters5/5

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

Schema coverage is 0%, but the description fully compensates. It explains the credentials dict's purpose, the cabinet parameter's default and fallback behavior, and the i_understand_key_goes_to_chat flag's requirement. Each parameter is given meaningful context.

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's purpose: to change or rotate an API key, with a concrete use case (expired or leaked). It distinguishes itself from sibling set_key tools (e.g., wb_set_key, ozon_set_key) by explicitly mentioning the marketplace and the security caveat.

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?

Provides explicit when-to-use guidance (key expired/leaked) and alternatives (installer, seller cabinet rotation). Also clarifies default behavior for cabinet selection, making it easy for an agent to decide when to call this tool.

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