Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

list_people_conversations

Retrieve conversation session IDs linked to a CRM contact using a people ID or email; inspect content or metadata with a separate conversation tool.

Instructions

Lists conversations linked to a CRM contact. Returns conversation session identifiers only; use a conversation tool to inspect their content or metadata.

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": {
      "people_id_or_email": "<people_id_or_email>"
    },
    "name": "list_people_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
people_id_or_emailYesThe CRM profile people identifier or email address ('people_id' value).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the return payload is identifiers only, which prevents an agent from expecting message bodies, but it says nothing about pagination, ordering, permission requirements, or what happens for an unknown contact or a contact with no conversations.

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 short sentences, front-loaded with purpose and immediately followed by the output constraint and hand-off. Nothing is redundant or padded.

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?

For a single-parameter read tool with no output schema, the description supplies the two things an agent most needs: the relationship it queries and the shape of what comes back. Only edge-case behavior (empty results, pagination) is left uncovered.

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 description coverage is 100% and the single parameter already documents that it accepts a people identifier or email. The phrase 'linked to a CRM contact' corroborates the parameter's meaning but adds no format, validation, or fallback detail beyond the schema.

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 names a specific verb and resource ('Lists conversations') and narrows scope to those 'linked to a CRM contact', which lets an agent distinguish it from the generic paginated conversation listers in the sibling set. It stops short of naming a specific sibling to route against, so the differentiation is implicit.

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 gives a clear use condition (when you have a CRM contact and want their conversations) and explicitly redirects content/metadata inspection to a separate conversation tool. No explicit exclusions, and the alternative is described by type rather than by name.

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