Skip to main content
Glama

get_conversations

Fetch a limited or filtered list of Xianyu conversations—sendable-only or product-context-only—to identify chats available for messaging and review active product discussions.

Instructions

获取会话列表

Args: limit: 数量限制 sendable_only: 是否仅返回可发送会话 context_only: 是否仅返回已有商品上下文的会话

Returns: 会话列表和状态

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": "get_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
context_onlyNo
sendable_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and largely drops it. It only says the call returns a conversation list and status; there is nothing about ordering, pagination/total counts, the effective default limit of 20, permissions, or whether the result is a live read.

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?

The Args/Returns structure is front-loaded and free of padding; every line maps to a real field. It is arguably over-terse rather than bloated, but nothing is wasted.

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

Completeness2/5

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

Three parameters, no annotations, no output schema, and 0% schema coverage mean the description is the only documentation channel, and it is thin. Return shape beyond "list and status", filtering interaction semantics, and the overlap with get_sendable_conversations are all left unaddressed.

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 description coverage is 0%, so the description must compensate, and it does translate all three parameters meaningfully — notably clarifying that context_only means conversations with existing product/item context. However it omits the default values, any bounds on limit, and what happens when sendable_only and context_only are combined.

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

Purpose3/5

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

"获取会话列表" is essentially a restatement of the tool name, though the Args block reveals the capability is more than a raw dump (filterable by sendable/context). It never distinguishes this from sibling get_sendable_conversations, which overlaps with the sendable_only flag and could confuse selection.

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

Usage Guidelines2/5

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

No statement of when to call this versus alternatives, no prerequisites, no exclusions. The existence of get_sendable_conversations alongside a sendable_only parameter is exactly the ambiguity the description should have resolved, and it does not.

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