Skip to main content
Glama

Intercom

by io.github.pipeworx-io

Ic Get Conversation

ic_get_conversation
Read-onlyIdempotent

Get complete conversation thread by ID. Returns all messages, timestamps, participants, and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesConversation ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoConversation ID
errorNoError code if connection required
stateNoConversation state
sourceNoSource of conversation
messageNoError message if connection required
created_atNoUnix timestamp when created
updated_atNoUnix timestamp when last updated
participantsNoParticipants in conversation
conversation_partsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "conversation_parts": {
+      "properties": {
+        "data": {
+          "description": "Array of message parts",
+          "items": {
+            "properties": {
+              "author": {
+                "type": "object"
+              },
+              "body": {
+                "type": "string"
+              },
+              "created_at": {
+                "type": "number"
+              },
+              "id": {
+                "type": "string"
+              },
+              "type": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "type": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "created_at": {
+      "description": "Unix timestamp when created",
+      "type": "number"
+    },
+    "error": {
+      "description": "Error code if connection required",
+      "type": "string"
+    },
+    "id": {
+      "description": "Conversation ID",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message if connection required",
+      "type": "string"
+    },
+    "participants": {
+      "description": "Participants in conversation",
+      "type": "object"
+    },
+    "source": {
+      "description": "Source of conversation",
+      "type": "object"
+    },
+    "state": {
+      "description": "Conversation state",
+      "type": "string"
+    },
+    "updated_at": {
+      "description": "Unix timestamp when last updated",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "123456789"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. Description adds detail on returned content (messages, timestamps, participants, metadata), which aligns with annotations. No contradictions.

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?

Two sentences, front-loaded purpose, no unnecessary words. Efficient and clear.

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?

Given presence of output schema, description adequately covers what the tool returns. Complete for a retrieval tool.

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?

Only one parameter (id) with schema coverage 100%. Description adds minimal value beyond schema (just 'by ID'). Baseline 3 is appropriate.

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?

Title and description clearly state 'Get complete conversation thread by ID' with specific returns (messages, timestamps, participants, metadata), distinguishing it from sibling tools like ic_list_conversations.

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?

Description implies use when you have a conversation ID and need full details. It does not explicitly state when not to use or mention alternatives, but context with siblings provides some guidance.

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

All Intercom toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route factual questions to the same underlying catalog with unclear boundaries. Polymarket tools also overlap (bet_research, polymarket_edges, polymarket_arbitrage), and ai_visibility_check vs scan_competitor_ai_presence are nearly the same operation.

Naming Consistency3/5

Most tools follow a readable snake_case verb_noun pattern (ask_pipeworx, entity_profile, resolve_entity, list_subscriptions). However, the set mixes two distinct naming families — ic_* for Intercom tools and pipeworx/* for the rest — and includes ambiguous generic names like remember/recall/forget that don't visually connect to the rest.

Tool Count2/5

36 tools is far more than needed for an Intercom-focused server; the vast majority have nothing to do with Intercom and instead cover a sprawling Pipeworx data-research, prediction-market, and memory/subscription toolkit. The count alone is in the 'too many' range, and the scope mismatch makes it feel even more inflated.

Completeness2/5

For a server named Intercom, the surface is severely incomplete: only read/list/search operations exist for contacts and conversations, with no create, update, delete, send-message, or company-detail operations. The unrelated Pipeworx tools are fairly broad, but they don't compensate for the missing Intercom lifecycle coverage that the server name promises.

Resources