Skip to main content
Glama

List conversations

list_conversations
Read-onlyIdempotent

Retrieve a store's customer conversations sorted by newest activity, filter by status, channel, and time window, and spot customers waiting for a human via pending handover.

Instructions

List the store's customer conversations, newest activity first. Use handover_status=pending to find customers waiting for a human. Returns a preview of the last message; call get_conversation for the full thread.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNoOnly conversations with activity in this window.
offsetNo
channelNo
handover_statusNo

Output Schema

NameRequiredDescriptionDefault
totalYes
has_moreYes
conversationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the description has a lower burden. It adds useful behavioral context: results are ordered by newest activity and include only a last-message preview, with full threads available via get_conversation.

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?

The description is three tightly written sentences with no filler. The main scope, filtering tip, return behavior, and sibling handoff are front-loaded and easy to scan.

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

Completeness3/5

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

This is a moderately complex list tool with five parameters and low schema description coverage, and the description omits pagination and filter semantics beyond handover_status. Output schema and annotations cover return format and safety, but the definition still leaves gaps for correct parameter use.

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 only 20%, so the description should compensate for undocumented parameters, but it only explains handover_status=pending meaningfully. It leaves limit, offset, since, and channel without added semantic guidance beyond their names and enum values.

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 states a specific verb and resource: listing the store's customer conversations, with ordering specified as newest activity first. It also distinguishes this tool from get_conversation by noting that this returns a preview while get_conversation returns the full thread.

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 gives explicit guidance to use handover_status=pending when looking for customers waiting for a human, and directs the agent to get_conversation for full threads. It does not explicitly state when not to use this tool, but the main alternative routing is clear.

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