Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

list_conversations_at_page

Lists workspace conversations by page so you can browse paginated results and optionally filter by inbox.

Instructions

Lists conversations in the workspace for one specified page. This tool is paginated, more entries can thus be retrieved.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_conversations_at_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoThe page number to list conversations at.
inbox_idNoThe inbox to list conversations from. Defaults to 'all' (includes all inboxes). Provide only when listing conversations from a specific inbox: an empty string for the Main inbox, '_internal:agent' for the Automated inbox, or a sub-inbox ID returned by list_inboxes.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the key trait that the tool is paginated and that more entries exist beyond one page, which is real value. However, it says nothing about page size, result ordering, total count, or what a returned conversation contains, so the disclosure is partial rather than rich.

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?

Two short sentences with the resource and pagination facts front-loaded; nothing is wasted. The second sentence's phrasing ("more entries can thus be retrieved") is slightly awkward but not costly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, read-only listing tool with no output schema and no annotations, the definition covers the essentials of what it returns and how paging works. It still omits ordering, page size, and the shape of a conversation entry, which an agent would want before choosing this over search_conversations or list_latest_conversations.

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%: the schema already explains page numbering, the 'all' default for inbox_id, and the special '' / '_internal:agent' / sub-inbox ID values. The description adds no additional meaning beyond noting that page-based iteration is supported, so the baseline 3 applies.

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 states a specific verb and resource ("Lists conversations in the workspace") and adds the scoping detail that results are returned one page at a time. It does not distinguish this tool from nearby siblings such as list_latest_conversations, list_people_conversations or search_conversations, leaving the agent to infer the distinction from names alone.

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?

There is no explicit when-to-use guidance and no statement about when not to use it or which sibling to prefer for a filtered or recency-based listing. The only usable cue is the pagination note, which implies the tool is for walking a full listing page by page, but that is left implicit.

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