Skip to main content
Glama

⚠️ BBIP: buy promotion

promotion_create_bbip_order_for_items_v1
Destructive

Creates a paid BBIP promotion order for Avito listings, charging the full budget from the account balance. Requires prior cost estimation from suggest and forecast tools.

Instructions

⚠️ PAID ACTION (money): creates a BBIP order to enable promotion for listings and CHARGES the budget from the account balance. The order is created only if there are no errors across all listings; if funds are insufficient — 402. FIRST estimate the cost and return for free: promotion_get_bbip_suggests_by_items_v1 (budget options) → promotion_get_bbip_forecasts_by_items_v1 (forecast). Then for each listing pass an option from suggests as {itemId, duration, oldPrice, price} (oldPrice/price — kopecks/day, duration — days; full budget = price × duration). Returns orderId (UUID) — check its status via promotion_get_order_status_v1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes1 to 100 listings for paid promotion. Each element is {itemId, duration, oldPrice, price} from promotion_get_bbip_suggests_by_items_v1. The whole order is rejected if any listing has an error.
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.
Behavior5/5

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

Description aligns with annotations (destructiveHint=true, readOnlyHint=false). It adds behavioral details: 'PAID ACTION (money)', 'CHARGES the budget', 'order is created only if no errors across all listings', and explains dryRun and idempotencyKey behavior beyond 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?

Single dense paragraph, front-loaded with warning, purpose, then procedural steps. Every sentence adds value. No fluff.

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?

Covers prerequisites, parallel tools, error handling, return value (orderId). Minor gap: could mention other potential error responses beyond 402. Still very complete given complexity.

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 100%, but description adds meaning: for 'items' it specifies the source (suggests) and formula; for 'dryRun' it explains preview; for 'idempotencyKey' it explains duplicate protection. All parameters are enriched beyond schema.

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 'creates', the resource 'BBIP order', and the action 'CHARGES the budget'. It distinguishes from sibling tools by referencing estimation and status-checking tools (promotion_get_bbip_suggests_by_items_v1, promotion_get_bbip_forecasts_by_items_v1).

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?

Explicit guidance: 'FIRST estimate the cost and return for free... Then for each listing pass an option...' It also describes error conditions (402 for insufficient funds) and prerequisites (use suggests). Alternatives are named for estimation and status checking.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elchin92/avito-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server