Skip to main content
Glama
Sign In
Avito MCP

Avito MCP

by elchin92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Discounts: campaign statistics

msg_discounts_open_api_stats
Read-onlyIdempotent

Get statistics for sent discount campaigns: offers sent, accepted, discount amount, cost, and dates. Analyze results over a specified period.

Instructions

[BETA] Returns statistics for already-sent discount/special-offer campaigns over a period (stats). Read-only; sends nothing and charges nothing. For each campaign: itemId, offerSlug, send and expiration dates, the number of offers sent (count) and accepted by buyers (accepted), the discount amount, and the cost. Use it to analyze results; for eligibility checks use ..._available, and for the remaining plan balance use ..._tariff_info.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dateTimeFrom": "<dateTimeFrom>",
      "dateTimeTo": "<dateTimeTo>"
    },
    "name": "msg_discounts_open_api_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateTimeToYesEnd of the selection period, RFC3339 / ISO 8601 format (e.g. 2022-03-01T12:00:00Z).
dateTimeFromYesStart of the selection period, RFC3339 / ISO 8601 format (e.g. 2022-02-24T05:00:00Z).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.3
  2. Removedv1.3.2
  3. Changed2 schema fields changedv0.8.0
    • changedInput schema / properties / dateTimeFrom / description
      Previous value: -"Начало периода (ISO 8601)."New value: +"Start of the selection period, RFC3339 / ISO 8601 format (e.g. 2022-02-24T05:00:00Z)."
    • changedInput schema / properties / dateTimeTo / description
      Previous value: -"Конец периода (ISO 8601)."New value: +"End of the selection period, RFC3339 / ISO 8601 format (e.g. 2022-03-01T12:00:00Z)."
  4. First observedv0.7.4

TDQS

A4.7/5.0
Behavior5/5

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

Declares read-only, no sends, no charges, and lists return fields. Annotations already indicate safety; description reinforces and adds detail.

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?

Short, front-loaded, no redundancy. Every sentence adds value: purpose, read-only note, return content, usage guidance.

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?

Describes return fields despite no output schema, provides usage context, and distinguishes siblings. Complete for a stats tool.

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

Parameters3/5

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

Schema covers both parameters with descriptions (100% coverage). Description does not add parameter-specific detail beyond stating the period, but baseline is adequate.

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 returns statistics for already-sent discount campaigns over a period, and distinguishes from sibling tools for eligibility checks and tariff info.

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 to use for analyzing results and provides alternatives for eligibility checks (msg_discounts_open_api_available) and remaining balance (msg_discounts_open_api_tariff_info).

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