Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List conversations

luca_conversations_list
Read-onlyIdempotent

Lists recent conversations with filters for channel, status, unread state, lead, and search text, returning cursor-based pages for review or triage.

Instructions

List recent conversations. Query supports limit, cursor, channel, and q.

Luca operation: GET /api/conversations Required scopes: conversations:read Required OAuth scope: luca:read; data sensitivity: full_content Does not require idempotency. Use workspaceId or workspaceSlug to override the default workspace configured by environment.

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": "luca_conversations_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
maxPagesNoMax pages the server auto-fetches and merges (default 10, hard cap 50). If more remain, the result is marked truncated with a nextCursor to continue.
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.

Output Schema

NameRequiredDescriptionDefault
resultYes
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.2
    • addedInput schema / properties / query / properties / channels
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / query / properties / status
      Added value: +{
+  "enum": [
+    "needs-input",
+    "luca",
+    "you"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / query / properties / unread
      Added value: +{
+  "enum": [
+    "true",
+    "false"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / result / properties / urgentConversations
      Added value: +{
+  "type": "array"
+}
    • changedOutput schema / properties / result / x-luca-redacted-fields
      Previous value: -[
-  "conversations[].lastMessagePreview",
-  "conversations[].leadDisplayName",
-  "conversations[].leadProfilePhotoUrl"
-]New value: +[
+  "conversations[].lastMessagePreview",
+  "conversations[].leadDisplayName",
+  "conversations[].leadProfilePhotoUrl",
+  "urgentConversations[].lastMessagePreview",
+  "urgentConversations[].leadDisplayName",
+  "urgentConversations[].leadProfilePhotoUrl"
+]
  2. Changed1 schema field changedv0.4.1
    • addedInput schema / properties / query / properties / leadId
      Added value: +{
+  "format": "uuid",
+  "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
+  "type": "string"
+}
  3. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds auth context (conversations:read and luca:read OAuth scope), data sensitivity (full_content), the underlying endpoint, and the default-workspace behavior — all real context beyond the annotations. "Does not require idempotency" is slightly redundant against idempotentHint=true but does not contradict it.

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?

Front-loaded with the core list statement and filter summary, then structured metadata lines. Short and skimmable, with only minor boilerplate ("Luca operation", "Does not require idempotency") that carries modest value.

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 read-only list tool with an output schema, a 4-parameter wrapper, and annotations covering safety, the description supplies auth scopes, data sensitivity, workspace resolution, and pagination hints (via maxPages in schema). Nothing critical for correct invocation is missing, though filter semantics for the many query sub-parameters remain thin.

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 75%, so the schema largely documents its own parameters; the description names only a subset (limit, cursor, channel, q) and adds no format or semantics for leadId, status, unread, channels, channelAccountId, or externalAccountId. It does clarify the workspace override intent, but overall adds little beyond the structured fields — baseline 3.

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?

"List recent conversations" states a specific verb and resource, and the mention of query filters (limit, cursor, channel, q) makes clear it is a filtered list rather than a single-record fetch. It never explicitly contrasts itself with luca_conversations_get, so it stops short of a 5.

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

Usage Guidelines3/5

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

The only usage guidance is the workspace override sentence ("Use workspaceId or workspaceSlug to override the default workspace configured by environment"), which is genuinely helpful. There is no statement of when to prefer this over luca_conversations_get or luca_conversations_messages, and no exclusions or prerequisites beyond scopes.

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

Deploy Server

Other Tools