Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Preview a lead import

luca_leads_import_preview
Read-onlyIdempotent

Preview a mapped CSV lead import before applying it.

Instructions

Preview a mapped CSV lead import before applying it.

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

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": {
      "body": "<body>"
    },
    "name": "luca_leads_import_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.

Output Schema

NameRequiredDescriptionDefault
resultYes
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.1
    • addedInput schema / properties / body / properties / rows / items / additionalProperties
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "object"
+    },
+    {
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedOutput schema / properties / result / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "object"
+  },
+  {
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observedv0.4.0

TDQS

B3.4/5.0
Behavior4/5

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

Adds real context beyond annotations: required scopes (leads:read, luca:draft), data sensitivity full_content, no idempotency requirement, and the default-workspace behavior with override options. It does not say what the preview actually validates or whether it persists anything, which matters for a 'preview' operation.

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-loads the one-line purpose, then lists operation metadata compactly. The workspace-override line is appended after the auth metadata rather than grouped with parameters, but overall there is little waste.

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?

An output schema exists so return values need not be explained, and scopes/workspace behavior are covered. However, for a tool whose main challenge is constructing a valid rows+mapping payload, the description says nothing about row limits, mapping requirements, or what the preview response is meant to be inspected for.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 67% and the bulk of the payload is a deeply nested body (rows, mapping.identity, identities, consents, customFields) with no field-level descriptions in the schema or the description. The description only restates the workspaceId/workspaceSlug override already documented in the schema, leaving the complex mapping semantics entirely unexplained.

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 (preview) and resource (mapped CSV lead import) and frames it as a pre-step 'before applying it', which implicitly distinguishes it from luca_leads_import_apply. It never names that sibling explicitly, so the discrimination relies on inference.

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 phrase 'before applying it' hints that this precedes luca_leads_import_apply, but the apply tool is never named and there are no stated conditions, prerequisites, or exclusions beyond that implication.

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