Skip to main content
Glama

List Alibaba conversations

alibaba_list_conversations
Read-onlyIdempotent

Lists Alibaba conversations from the open messenger tab, including chats not visible on screen, without switching the active chat. Requires read or read/write access.

Instructions

List Alibaba conversations from the open messenger tab, including chats that are not on screen. Requires read or read/write access. This does not switch the open chat.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "alibaba_list_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description still adds real context beyond them: the data source is the open messenger tab, off-screen chats are included, an access level is required, and the active chat is left unchanged. It omits pagination/limit behavior, which keeps it short of a 5.

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 short sentences with no filler; the scope statement comes first, followed by the access requirement and the side-effect clarification. Every clause earns its place.

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?

For a simple two-optional-parameter read tool with no output schema, the description covers source, scope, permissions and non-effects adequately. The remaining gap is filter semantics and result-set size, which matters for an agent deciding whether one call suffices.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden for the two parameters, yet it never mentions 'limit' or 'search'. An agent must guess what 'search' matches (contact name, message text, group title) and cannot tell whether 'limit' truncates results or how the default of 30 behaves.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List Alibaba conversations') plus a scope qualifier that matters: it reads from the open messenger tab and includes chats not currently on screen. The closing clause ('does not switch the open chat') implicitly contrasts it with tools that navigate into a conversation, though no sibling is named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a prerequisite ('requires read or read/write access') and clarifies a non-effect ('does not switch the open chat'), which implies a passive enumeration use case. However, it never states when to prefer this over alibaba_get_conversation or how it relates to the attachment-listing sibling, leaving the routing decision to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.