Skip to main content
Glama

Read Alibaba conversation

alibaba_get_conversation
Read-onlyIdempotent

Retrieve a full Alibaba conversation by ID, including off-screen messages in oldest-first order, without switching the open chat. Use an ID from the conversation list.

Instructions

Read one conversation by id, including messages that are not on screen. Messages come back oldest first. This does not switch the open chat. Requires read or read/write access. Use an id from alibaba_list_conversations.

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": {
      "conversationId": "<conversationId>"
    },
    "name": "alibaba_get_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
conversationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which already declare read-only, idempotent, non-destructive), the description adds genuine behavioral detail: off-screen messages are included, results are ordered oldest first, the open chat is not switched, and read or read/write access is required. These are all non-obvious traits an agent could not derive from the structured fields.

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?

Five short declarative sentences, front-loaded with the core purpose followed by ordering, side-effect, permission, and input-source facts in order of importance. No filler or redundant restatement of the tool name.

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?

With no output schema and no annotations gaps on safety, the description covers what an agent needs to call it correctly: input source, ordering of returns, permission requirement, and the non-side-effect of not switching chats. The main omission is any guidance on the undocumented limit parameter and pagination behavior.

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 must carry the parameter burden. It only clarifies that conversationId should come from alibaba_list_conversations, and never mentions the limit parameter (default 100, max 500), leaving an agent unaware that result size is controllable or truncatable.

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 opens with a specific verb and resource ('Read one conversation by id') and immediately scopes the result set ('including messages that are not on screen'), which distinguishes it from its list/send siblings. An agent can tell what this tool returns without inspecting the schema.

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

Usage Guidelines4/5

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

It explicitly directs the agent to obtain the identifier from alibaba_list_conversations, giving a concrete precondition rather than leaving input sourcing to inference. It does not state when-not to use it or contrast with siblings like alibaba_send_message, so it falls short of a full 5.

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