Skip to main content
Glama
elchin92

Avito MCP

by elchin92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Profile spendings

items_post_account_spendings
Read-onlyIdempotent

View your Avito account spendings over a chosen period, grouped daily, weekly, or monthly and broken down by spending type. Read-only: shows only incurred costs.

Instructions

Returns a REPORT of the profile's spendings over a period by Avito spending category: all, promotion, presence, commission, or rest. Read-only, spends no money (only shows already incurred spending). Period dateFrom..dateTo (YYYY-MM-DD). Note: grouping here is a STRING "day"|"week"|"month" (NOT an object, unlike items_post_item_analytics). Data depth no more than 270 days, no more than 1 request per minute. Required: dateFrom, dateTo, spendingTypes, grouping.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateToYesEnd of the period, inclusive (YYYY-MM-DD).
filterNoOptional selection filters: categoryIDs — category IDs, itemIDs — listing IDs, locationIDs — location IDs. employeeIDs is NOT supported here. Without the filter — spendings of the entire profile.
user_idNoID of the owner user. Defaults to Profile_id from .env.
dateFromYesStart of the period, inclusive (YYYY-MM-DD); no more than 270 days back.
groupingYesGroup spendings by period — a string (required): day (by day), week (by week), month (by month).
spendingTypesYesSpending categories from the Avito contract (at least 1): all, promotion, presence, commission, rest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / spendingTypes / description
      Previous value: -"Spending types for the report (at least 1): vas, perf_vas, lf, cv, tariff, subscription, cpa, bundle."New value: +"Spending categories from the Avito contract (at least 1): all, promotion, presence, commission, rest."
    • addedInput schema / properties / spendingTypes / items / enum
      Added value: +[
+  "all",
+  "promotion",
+  "presence",
+  "commission",
+  "rest"
+]
  2. Changed9 schema fields changedv0.8.0
    • changedInput schema / properties / dateFrom / description
      Previous value: -"Начало периода (YYYY-MM-DD)."New value: +"Start of the period, inclusive (YYYY-MM-DD); no more than 270 days back."
    • changedInput schema / properties / dateTo / description
      Previous value: -"Конец периода (YYYY-MM-DD)."New value: +"End of the period, inclusive (YYYY-MM-DD)."
    • changedInput schema / properties / filter / description
      Previous value: -"Фильтры по категориям / объявлениям / локациям (employeeIDs НЕ поддерживается)."New value: +"Optional selection filters: categoryIDs — category IDs, itemIDs — listing IDs, locationIDs — location IDs. employeeIDs is NOT supported here. Without the filter — spendings of the entire profile."
    • changedInput schema / properties / filter / properties / categoryIDs / description
      Previous value: -"Фильтр по ID категорий."New value: +"Filter by category IDs."
    • changedInput schema / properties / filter / properties / itemIDs / description
      Previous value: -"Фильтр по ID объявлений."New value: +"Filter by listing IDs."
    • changedInput schema / properties / filter / properties / locationIDs / description
      Previous value: -"Фильтр по ID локаций."New value: +"Filter by location IDs."
    • changedInput schema / properties / grouping / description
      Previous value: -"Группировка расходов по периоду: \"day\" | \"week\" | \"month\" (строка, обязательно)."New value: +"Group spendings by period — a string (required): day (by day), week (by week), month (by month)."
    • changedInput schema / properties / spendingTypes / description
      Previous value: -"Типы расходов: vas, perf_vas, lf, cv, tariff, subscription, cpa, bundle."New value: +"Spending types for the report (at least 1): vas, perf_vas, lf, cv, tariff, subscription, cpa, bundle."
    • changedInput schema / properties / user_id / description
      Previous value: -"По умолчанию — Profile_id из .env."New value: +"ID of the owner user. Defaults to Profile_id from .env."
  3. First observedv0.7.4

TDQS

A4.2/5.0
Behavior4/5

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

Description adds beyond annotations: specifies data depth limit, rate limit, and that grouping is a string format. Annotations already cover safety (readOnlyHint=true, destructiveHint=false), so description's additional constraints are useful but not critical.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise, front-loaded with main purpose, and packs relevant details efficiently. Could be better structured with bullet points but remains dense and informative.

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

Completeness3/5

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

Despite high schema coverage and annotations, the tool lacks an output schema. Description does not detail the returned report structure or fields, leaving the agent without full context on what to expect.

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 coverage is 100% and descriptions in schema are detailed. Description reiterates required parameters and format but adds little new meaning beyond what is in the 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?

Clearly states it returns a REPORT of profile's spendings over a period by Avito spending category, with specific verb and resource. Notes difference from sibling tool items_post_item_analytics regarding grouping format, aiding differentiation.

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 states when to use (read-only, no money spent), provides period format, data depth limit (270 days), rate limit (1 per minute), and required parameters. Also clarifies exclusions like employeeIDs not supported in filter.

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