Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a broadcast

luca_broadcasts_create

Creates a broadcast draft for a campaign, requiring campaign ID and name; optionally set audience segments and idempotency for safe retries.

Instructions

Create a broadcast draft. Body requires campaignId and name.

Luca operation: POST /api/broadcasts Required scopes: broadcasts:write Required OAuth scope: luca:queue_ops; data sensitivity: full_content Requires Idempotency-Key. Provide idempotencyKey for safe retries, or the server will generate one. 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_broadcasts_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.
idempotencyKeyNoStable key for safe retries. If omitted, the MCP server generates a unique key for this call.

Output Schema

NameRequiredDescriptionDefault
resultYes
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.2
    • addedOutput schema / properties / result / properties / billingPaused
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / result / properties / outcomes
      Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "callsBooked": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "replied": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "windowDays": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
  2. Changed4 schema fields changedv0.4.1
    • addedInput schema / properties / body / properties / segment / properties / groups / items / properties / rules / items / properties / value / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "object"
+  },
+  {
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / body / properties / segment / properties / rules / items / properties / value / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "object"
+  },
+  {
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedOutput schema / properties / result / properties / retryBlockedReason
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / result / x-luca-redacted-fields
      Previous value: -[
-  "recipients[].messageBody",
-  "safetyReport.findings[].evidence",
-  "sampleMessages[].body",
-  "segmentSnapshot.excludedRecipients[].displayName",
-  "segmentSnapshot.leads[].customFields",
-  "segmentSnapshot.leads[].displayName",
-  "segmentSnapshot.leads[].messageBody"
-]New value: +[
+  "recipients[].messageBody",
+  "safetyReport.findings[].evidence",
+  "sampleMessages[].body",
+  "segmentSnapshot.excludedRecipients[].displayName",
+  "segmentSnapshot.leads[].customFields",
+  "segmentSnapshot.leads[].displayName",
+  "segmentSnapshot.leads[].messageBody",
+  "segmentSnapshot.leads[].templateMapping",
+  "segmentSnapshot.leads[].templatePart"
+]
  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?

Goes beyond the annotations by disclosing required scopes (broadcasts:write, luca:queue_ops), data sensitivity (full_content), and the Idempotency-Key requirement with server-side key generation. That is genuinely useful operational context for a write tool. Minor tension with idempotentHint=false is not a real contradiction, since a supplied idempotency key governs retry safety rather than the operation being inherently idempotent.

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 action and required body fields, then grouped operational metadata (endpoint, scopes, idempotency, workspace override). The endpoint/scope/sensitivity lines read as boilerplate but each carries a distinct constraint, so little is truly wasted.

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 mutation tool with annotations and an output schema, the description covers safety-relevant facts (scopes, idempotency, workspace targeting) and the required body fields. The gap is the nested segment/filter structure, which is left wholly to the schema despite being the main source of misuse risk.

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?

Adds real meaning for idempotencyKey and the workspaceId/workspaceSlug override (explaining these take precedence over the environment default), and restates the required body fields campaignId and name. However, the large nested segment/groups filter object, batchSize, canarySize and personalizationMode get no explanation at all, leaving the most complex part of the body entirely to 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 plus a meaningful scope qualifier: it creates a *draft*, which implicitly separates it from luca_broadcasts_launch/approve. It does not name those siblings explicitly, so differentiation is inferable rather than stated.

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 'draft' framing implies this is the first step before launch/preview, but there is no explicit when-to-use or when-not-to-use guidance, and no stated prerequisites (e.g. that the campaignId must reference an existing campaign). Scopes and workspace override are covered, but selection guidance against siblings is absent.

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