Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List the review queue

luca_review_queue_list
Read-onlyIdempotent

Lists review-queue items with filters for status, category, order, lead, and workspace, enabling triage of pending sales conversations and paginated continuation.

Instructions

List review-queue items when the API key has review queue access.

Luca operation: GET /api/review-queue Required scopes: review_queue: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_review_queue_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. Changed1 schema field changedv0.4.2
    • changedOutput schema / properties / result / x-luca-redacted-fields
      Previous value: -[
-  "items[].criticIssues",
-  "items[].draftBody",
-  "items[].draftContent",
-  "items[].draftParts",
-  "items[].leadDisplayName",
-  "items[].media",
-  "items[].mediaContext",
-  "items[].objectionVariants",
-  "items[].qualification",
-  "items[].safetyFindings",
-  "items[].signals"
-]New value: +[
+  "items[].criticIssues",
+  "items[].draftBody",
+  "items[].draftContent",
+  "items[].draftParts",
+  "items[].lastInboundMessages",
+  "items[].leadDisplayName",
+  "items[].leadProfilePhotoUrl",
+  "items[].media",
+  "items[].mediaContext",
+  "items[].objectionVariants",
+  "items[].qualification",
+  "items[].safetyFindings",
+  "items[].sentBody",
+  "items[].signals"
+]
  2. Changed5 schema fields 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"
+}
    • addedInput schema / properties / query / properties / status / enum
      Added value: +[
+  "pending",
+  "approved",
+  "rejected",
+  "sent",
+  "superseded",
+  "stale"
+]
    • removedInput schema / properties / query / properties / status / minLength
      Removed value: -1
    • addedOutput schema / properties / result / properties / asOf
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / result / x-luca-redacted-fields
      Previous value: -[
-  "items[].criticIssues",
-  "items[].draftBody",
-  "items[].draftParts",
-  "items[].leadDisplayName",
-  "items[].media",
-  "items[].mediaContext",
-  "items[].objectionVariants",
-  "items[].qualification",
-  "items[].safetyFindings",
-  "items[].signals"
-]New value: +[
+  "items[].criticIssues",
+  "items[].draftBody",
+  "items[].draftContent",
+  "items[].draftParts",
+  "items[].leadDisplayName",
+  "items[].media",
+  "items[].mediaContext",
+  "items[].objectionVariants",
+  "items[].qualification",
+  "items[].safetyFindings",
+  "items[].signals"
+]
  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 readOnly, idempotent and non-destructive, but the description adds what they cannot: required scopes (review_queue:read, luca:read), full_content data sensitivity, and that idempotency is not required. Workspace defaulting behaviour is also disclosed, though pagination/truncation semantics live only in the schema.

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 purpose in the first line, then a scannable block of operation, scopes, idempotency and workspace override. A few lines are boilerplate metadata, but nothing is wasted or buried.

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?

Output schema exists, so return shape need not be explained, and annotations carry the safety profile. With auth scopes, operation path, sensitivity and workspace override covered, an agent has what it needs to call this correctly; only sibling disambiguation is absent.

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% and the three top-level params (maxPages, workspaceId, workspaceSlug) are already described in the schema. The description's one addition is that workspaceId/workspaceSlug override the environment-configured default, which is useful but modest; the nested query filters (status, category, order, leadId) get nothing 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?

States a specific verb and resource ('List review-queue items') plus the underlying operation GET /api/review-queue, so the read semantics are unambiguous. It does not distinguish itself from read-adjacent siblings such as luca_review_queue_summary or luca_review_queue_changes, which an agent would have to reason about on its own.

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?

Gives a precondition ('when the API key has review queue access') and the scope needed, which is real gating guidance. It never says when to choose this over the sibling summary/changes endpoints, so selection between them is left implied.

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