Skip to main content
Glama

TrxPromo: commissions

trxpromo_get_commissions
Read-onlyIdempotent

Check promo availability and commission limits for Avito listings. Returns allowed minimum, maximum, and step values before applying a transactional promo.

Instructions

Checks transactional promo availability and the allowed commission range for listings (trxpromo_get_commissions, read-only — does not start anything or charge any fee). For each listing it returns the promoAvailable flag and settings: minimum/maximum/step of the commission in hundredths of a percent (100 = 1%). Use before trxpromo_apply to learn the commission limits. Start promo with trxpromo_apply, cancel with trxpromo_cancel. This is a GET with a request body — non-standard, but that is exactly how it is defined in the Avito swagger.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIDsYesArray of Avito listing IDs to check for promo availability and commission limits.
Behavior5/5

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

Description confirms read-only nature ('does not start anything or charge any fee'), aligning with annotations. Adds critical non-standard HTTP detail: 'GET with a request body', which annotations do not cover. No contradiction.

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, each earning its place. Front-loaded with purpose, no redundant words.

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?

For a read-only query tool with one parameter, description provides usage order, return format, behavioral nuance (non-standard HTTP), and sibling references. Complete despite absence of output schema.

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 covers parameter with description, but description adds output context: 'returns promoAvailable flag and settings: minimum/maximum/step of the commission in hundredths of a percent (100 = 1%)', which goes 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?

Description clearly states verb 'checks' and resource 'transactional promo availability and allowed commission range for listings'. Differentiates from siblings trxpromo_apply and trxpromo_cancel by naming them.

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?

Explicitly says 'Use before trxpromo_apply to learn the commission limits' and names start/cancel tools as alternatives, providing clear when-to-use guidance.

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