Skip to main content
Glama
commentkeyword-mcp

commentkeyword-mcp

Official

Get an AI agent conversation

get_conversation
Read-only

Retrieve a single DM conversation by ID from a conversation list or webhook event, including the contact, agent, keyword, collected data, and transcript.

Instructions

Get one DM conversation by id (from list_conversations, or the conversationId of a webhook event): the contact, the agent and keyword, the collected data and the transcript, oldest message first (the latest 1,000 at most).

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

Input Schema

NameRequiredDescriptionDefault
idYesThe conversation id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered, and the description adds real behavior on top: transcripts are returned oldest message first and truncated to the latest 1,000 messages. That cap is a concrete, non-obvious behavioral trait that affects how an agent should interpret results.

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?

One sentence, front-loaded with the action and resource, then the response contents and the ordering/limit constraint. No filler or restatement of the tool name beyond what is needed to specify scope.

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?

There is no output schema, so the description carries the burden of describing returns — and it does, listing the contact, agent/keyword, collected data, and transcript along with ordering and the 1,000-message ceiling. For a single-parameter read tool, nothing an agent needs to call or interpret it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single id parameter, so the baseline is 3; the description earns an extra point by explaining provenance of the id (from list_conversations or a webhook event's conversationId), which the schema's "The conversation id." does not convey. No format or UUID detail is added, but the schema already carries that.

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 gives a specific verb and resource ("Get one DM conversation by id") and enumerates what the response contains: contact, agent and keyword, collected data, and transcript. The singular "one DM conversation" implicitly sets it apart from list_conversations, which it also names as the id source, so an agent can distinguish fetch-by-id from listing.

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 tells the agent where the required id comes from — list_conversations or the conversationId of a webhook event — which is exactly the prerequisite an agent needs before calling. It stops short of stating when not to use it or naming other retrieval alternatives, so it is clear context rather than full routing guidance.

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