Skip to main content
Glama

octadezx_list_conversations

Read-onlyIdempotent

Retrieve recent or escalated customer conversations from a connected OctaDezx Cloud workspace across messaging and voice channels to triage support queues and fetch thread IDs before replying.

Instructions

Retrieve recent or escalated customer conversations from your connected OctaDezx Cloud workspace across WhatsApp, Instagram, Facebook Messenger, Telegram, Phone Voice, and Web Widget. Use when triaging open support queues or fetching thread IDs before replying. Requires OCTADEZX_API_KEY in the environment; if unset, returns a structured 'requires_api_key' guidance payload instead of failing silently.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of conversation threads to return (1 to 100, default 10).
statusNoFilter workspace conversations by triage state ('open', 'escalated', or 'all').all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / default
      Added value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum conversations to return (default 10)"New value: +"Maximum number of conversation threads to return (1 to 100, default 10)."
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / status / default
      Added value: +"all"
    • changedInput schema / properties / status / description
      Previous value: -"Filter by conversation status"New value: +"Filter workspace conversations by triage state ('open', 'escalated', or 'all')."
  2. Changed2 schema fields changedv1.1.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum conversations to return (default 20)"New value: +"Maximum conversations to return (default 10)"
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status"New value: +"Filter by conversation status"
  3. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds genuinely new operational context: the OCTADEZX_API_KEY requirement and the specific degraded behavior (a structured 'requires_api_key' payload rather than a silent failure). It omits pagination/cursor behavior and any rate-limit notes, which keeps it off 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 sentences, front-loaded with what the tool returns and the channels, then usage, then the environmental prerequisite. Every sentence carries distinct information with no restatement of the title or schema.

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 two-parameter read tool with no output schema, the definition covers scope, channels, usage triggers, and the API-key failure path. The only real gap is what the returned thread objects contain beyond IDs, which matters somewhat because no output schema exists.

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 coverage is 100%, so both the limit bounds and the status enum are fully documented in the schema. The description only echoes the status notion via 'recent or escalated' and adds no syntax, default, or interaction detail beyond that — baseline 3 applies.

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?

States a specific verb ('Retrieve') and resource ('recent or escalated customer conversations') and enumerates the six connected channels, making the read-only listing scope unmistakable. An agent can separate this from mutation siblings like octadezx_send_customer_reply or octadezx_trigger_voice_call without opening a 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?

'Use when triaging open support queues or fetching thread IDs before replying' gives two concrete triggering situations and implicitly positions it as the precursor to a reply tool. It stops short of naming an alternative tool or stating when not to use it, so it is clear context without explicit exclusions.

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