Skip to main content
Glama

List chats

messenger_get_chats_v2
Read-onlyIdempotent

Retrieve a list of your Avito chats with a preview of the last message and unread count. Filter by item, type, or unread status, and paginate results.

Instructions

Returns a LIST of the account's chats (conversations with buyers) with a preview of the last message and an unread counter. Read-only — sends nothing and does not mark anything as read. Use it to find the needed chat_id before messenger_get_messages_v3, messenger_post_send_message or messenger_chat_read. To get the details of a single known chat, use messenger_get_chat_by_id_v2. Supports filters (items, types, unread) and offset-based pagination via limit/offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idsNoFilter: CSV list of item IDs, returns chats for these items only (e.g. "12345,6789"). Defaults to all chats.
limitNoHow many chats to return per page (1–100, default 100).
offsetNoPagination offset: skip N chats (default 0).
unread_onlyNotrue — return only chats with unread messages; false/omitted — all chats.
chat_typesNoFilter by chat type, CSV: u2i (conversation about an item), u2u (conversation between users). Defaults to all types.
user_idNoAvito account ID whose chats are requested. Defaults to Profile_id from .env.
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it sends nothing and does not mark as read, plus notes offset-based pagination. This adds some context beyond annotations but not extensive behavioral details.

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?

Multiple sentences each provide essential information: main purpose, safety, usage pattern, alternative tool, supported features. Front-loaded and no redundancy.

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 return content, safety, usage context, alternatives, filtering, and pagination. Lacks explicit output schema details, but the description implies chat ids and preview fields. Sufficiently complete for a list tool with rich annotations.

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?

Input schema covers all 6 parameters with descriptions (100% coverage). The description groups filters and pagination but does not add significant new meaning beyond what schema provides.

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 a list of chats with specific details (preview of last message, unread counter), specifies it is read-only, and differentiates from sibling tools like messenger_get_chat_by_id_v2 and messenger_get_messages_v3.

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 this tool to find chat_id before other operations and points to messenger_get_chat_by_id_v2 for single chat details, providing clear when-to-use and when-not-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