Skip to main content
Glama

Intercom

by io.github.pipeworx-io

Ic List Conversations

ic_list_conversations
Read-onlyIdempotent

List conversations with pagination. Returns conversation ID, participants, status, created date, and last message preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
per_pageNoResults per page (default 20)
starting_afterNoPagination cursor

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError code if connection required
pagesNo
messageNoError message if connection required
conversationsNoList of conversations

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": {
+    "conversations": {
+      "description": "List of conversations",
+      "items": {
+        "properties": {
+          "created_at": {
+            "description": "Unix timestamp when created",
+            "type": "number"
+          },
+          "id": {
+            "description": "Conversation ID",
+            "type": "string"
+          },
+          "participants": {
+            "description": "Participants in conversation",
+            "type": "object"
+          },
+          "preview": {
+            "description": "Last message preview",
+            "type": "string"
+          },
+          "source": {
+            "description": "Source of conversation",
+            "type": "object"
+          },
+          "state": {
+            "description": "Conversation state (open/closed)",
+            "type": "string"
+          },
+          "updated_at": {
+            "description": "Unix timestamp when last updated",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "description": "Error code if connection required",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message if connection required",
+      "type": "string"
+    },
+    "pages": {
+      "properties": {
+        "next": {
+          "description": "Next page cursor",
+          "type": "object"
+        },
+        "type": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "per_page": 20
+  },
+  {
+    "per_page": 50,
+    "starting_after": "WzE2NzM5NDcyMjAwMCwgIjVkNzk4YzJhMjEwMDAwMDAxMDAwMDAwMCJd"
+  }
+]
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this as read-only, idempotent, etc. The description adds return field details but doesn't disclose any other behavioral traits like pagination characteristics or potential rate limits. It provides modest additional context.

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?

The description is very concise with a single sentence that covers the tool's action and return values. No wasted words, though it could be structured slightly more for readability.

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?

Given the output schema exists, the description sufficiently covers the tool's purpose and return fields. It mentions pagination but could clarify cursor behavior. Overall, adequate for a simple list 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?

Schema coverage is 100%, so the description doesn't need to add much. It mentions pagination but doesn't elaborate on parameter usage beyond what the schema already provides. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'List' and the resource 'conversations', and specifies the returned fields. While it doesn't explicitly differentiate from sibling tools like ic_get_conversation, the function name and return info make it distinguishable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives, such as ic_get_conversation for a single conversation or other list tools. The description only implicitly conveys usage through the verb 'List'.

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