Intercom

Retrieves detailed content for a specific resource identified by the given ID. Supports both conversation and contact IDs with 'conversation_' or 'contact_' prefixes.

Fetch a single Intercom contact by ID through the MCP server.

Fetch a single Intercom conversation by ID through the MCP server.

Purpose 1. Search for resources in Intercom (conversations and contacts) using a unified query approach. 2. Only a subset of properties will be returned in search results. 3. Use the Fetch tool with the returned IDs to get full details.

Usage 1. MUST specify object_type:conversations OR object_type:contacts to indicate which API to call. 2. Use specific field searches for precise filtering (e.g., email:john@example.com). 3. Use the starting_after parameter for pagination when more results exist. 4. Combine multiple search criteria with logical operators for complex queries.

Search Tool Response 1. Returns results with id, title, text, and url for each match. 2. IDs are prefixed with conversation_ or contact_ to indicate type. 3. Use these IDs with the Fetch tool to get complete resource details.

Intercom Search Query DSL Specification * Tokens are space-separated * Each token: key[:op]:value * op (optional, default = eq) ∈ { eq, neq, gt, lt, in, nin, contains } * value: * Unquoted: alphanumeric, no spaces * Quoted: use single or double quotes to include spaces

Common Parameters * object_type (mandatory) → "conversations" or "contacts" * q / query → free-text search across key fields * created_at / updated_at → timestamp filters (YYYY-MM-DD or Unix timestamp) * limit → max results (default: 10, max: 150) * starting_after → pagination cursor

Conversation Search (object_type:conversations) Supported Fields: * id * state → "open", "closed", "snoozed" * priority → "priority", "not_priority" * source_type → "conversation", "email", "facebook", "twitter", etc. * source_author_name * source_author_email * source_subject * source_body * contact_ids * statistics_time_to_assignment * statistics_time_to_admin_reply * statistics_time_to_first_close

Contact Search (object_type:contacts) Supported Fields: * id * name * email * email_domain * phone * role → "user", "lead" * custom_attributes.* → any custom field (e.g., custom_attributes.company)

Examples

Basic

user: show me recent conversations query: object_type:conversations created_at:gt:1735689600

Open email conversations

user: find open conversations from email query: object_type:conversations state:open source_type:email

Email domain filter

user: search for conversations from support emails query: object_type:conversations source_author_email:contains:"@support"

Slow response

user: find conversations with slow response times query: object_type:conversations statistics_time_to_admin_reply:gt:3600

Subject/body match

user: find conversations about billing query: object_type:conversations source_subject:contains:"billing" user: find conversations mentioning refund query: object_type:conversations source_body:contains:"refund"

Contact search

user: find contacts named John query: object_type:contacts name:"John" user: find contacts from example.com domain query: object_type:contacts email_domain:"example.com" user: find contacts with specific custom attribute query: object_type:contacts custom_attributes.plan_status:"active" user: recent contact activity query: object_type:contacts updated_at:gt:1735689600 limit:50

Contact-conversation link

user: find conversations for a specific contact query: object_type:conversations contact_ids:in:d2e3bde8-4fe4-4a74-9232-5f7458e7a4cb

Unsupported Features * Complex boolean logic beyond simple AND/OR * Fuzzy matching or proximity search * Aggregation or analytics queries * Full-text search across conversation content (use source fields instead) * Real-time or streaming results Intercom Search Query DSL specification. MUST start with object_type:conversations or object_type:contacts to specify which API to call. Use tokens separated by spaces with key[:op]:value format. Examples: 'object_type:contacts email:contains:"@example.com"' for domain search, 'object_type:conversations state:open created_at:gte:2024-01-01' for recent open conversations.

Search Intercom contacts through the MCP-backed tool surface.

Search Intercom conversations through the MCP-backed tool surface. Use this when the MCP server is the source of truth for search and you need to pass through structured filters without flattening them into the native connector model.