Related Servers

Each tool has a clearly distinct purpose, even those with similar themes (e.g., list_child_accounts vs. list_child_accounts_with_balances, or the three stats tools) are explicitly differentiated by their descriptions, which highlight what each returns and when to use it. The generic raw_request is deliberately scoped for endpoints without dedicated tools, so it does not conflict with the specialized ones.

All tool names follow a consistent snake_case verb_noun pattern (list_*, get_*, create_*, change_*, transfer_*, set_*, delete_*, add_*, etc.). Even less standard names like raw_request and auth_status are consistent in style and clearly convey their function, with no mixing of conventions.

With 26 tools, the count is slightly above the typical 3-15 range but is appropriate given the broad scope of the Avito Ads API, covering account management, user access, advertisers, contracts, campaigns, groups, creatives, transfers, and statistics. The tools are not redundant; each covers a distinct aspect, and the count feels justified rather than bloated.

The tool set covers the core lifecycle and management operations for the advertising domain, including CRUD where supported, listing, statistics, and financial transfers. The inclusion of raw_request provides access to any additional API endpoints, ensuring no dead ends or missing operations that would cause agent failures. The only gaps (e.g., lack of dedicated update/delete for some resources) are bypassed by raw_request.