Skip to main content
Glama

Get conversation

get_conversation
Read-onlyIdempotent

Get one conversation by its number: status, priority, inbox_id, labels, the assignee (a person), ai_assignee (the AI agent answering it), team and contact (id and name each, null when unset), unread_count, and created_at / last_activity_at as unix seconds.

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "get_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional: return only these fields of each record.
conversation_idYesThe conversation number shown in the dashboard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fields / items / enum
      Previous value: -[
      -  "id",
      -  "status",
      -  "priority",
      -  "inbox_id",
      -  "labels",
      -  "assignee",
      -  "team",
      -  "contact",
      -  "created_at",
      -  "last_activity_at",
      -  "unread_count"
      -]New value: +[
      +  "id",
      +  "status",
      +  "priority",
      +  "inbox_id",
      +  "labels",
      +  "assignee",
      +  "ai_assignee",
      +  "team",
      +  "contact",
      +  "created_at",
      +  "last_activity_at",
      +  "unread_count"
      +]
  2. First observed

TDQS

A4/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 closed-world, so the safety profile is covered. The description adds genuinely useful behavior context beyond that: which fields come back, that assignee is a person while ai_assignee is the AI agent, that object fields carry both id and name, that unset relations are null, and that timestamps are unix seconds.

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?

A single front-loaded sentence: verb and resource first, then the payload inventory. The long field enumeration is dense but earns its place because there is no output schema; minor cost is a run-on colon list that is harder to scan than a short bulleted shape.

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

Completeness5/5

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

With no output schema, the description effectively serves as return-value documentation, covering field set, nesting shape, null semantics, and timestamp units for a simple two-parameter read tool. Nothing an agent needs in order to call it correctly is missing, aside from not-found behavior, which is minor.

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%, with conversation_id documented as the dashboard number and fields documented as a field projection list. The description reinforces what conversation_id refers to but never mentions the optional fields parameter, so it adds little beyond the schema baseline.

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?

"Get one conversation by its number" gives a specific verb, resource, and cardinality, and the following field list makes clear this is a single-record detail fetch rather than a list or filter operation like conversation_list. An agent can distinguish it from the sibling listing tools without opening any schema.

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?

Usage is only implied: "by its number" suggests the agent must already have a conversation id, presumably from a list/search tool. There is no explicit when-to-use, when-not-to-use, or named alternative for fetching details of a single conversation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources