Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Publish a campaign

luca_campaigns_publish
Destructive

Freeze a campaign draft as an immutable version and point new enrollments to it, verifying provider capabilities first.

Instructions

Freeze the draft as a new immutable version and point new enrollments at it. Published versions never change. A live campaign reaches real leads through enrollments and through inbound DMs, comments, or story replies that match its trigger. Publish is blocked when the target provider cannot do something the campaign needs, so read the provider capabilities first.

Luca operation: POST /api/campaigns/{id}/publish Required scopes: campaigns:write Required OAuth scope: luca:queue_ops; data sensitivity: redacted Requires Idempotency-Key. Provide idempotencyKey for safe retries, or the server will generate one. Destructive: has a real-world side effect. You must pass confirm: true; the call is rejected without it. 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": {
      "id": "<id>"
    },
    "name": "luca_campaigns_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNoThis tool has a real-world side effect: it messages real leads, books, moves, or cancels a call, changes a lead's consent, imports leads, writes to a connected calendar or CRM, sends workspace events to an outside URL, or re-triggers downstream automations. Pass confirm: true to proceed; the call is rejected without it.
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint, openWorldHint, idempotentHint=false), it discloses real behavior: publication is irreversible because versions never change, live campaigns reach real leads via enrollments and inbound DMs/comments/story replies, provider-capability gaps block publishing, and an Idempotency-Key is required or server-generated. It also names the required scopes (campaigns:write, luca:queue_ops), which annotations cannot convey.

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?

Behavior is front-loaded in the first two sentences, then operational requirements are listed in scannable lines. There is some redundancy — the confirm:true requirement is stated in the description and again in the confirm parameter's schema description — but no sentence is wasted.

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

Completeness5/5

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

For a destructive mutation with five parameters and an output schema, the description covers everything an agent needs before calling: preconditions, immutability, auth scopes, workspace override, idempotency, and the confirmation gate. Return values are covered by the output schema, so no gap remains.

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 80%, so confirm, workspaceId, workspaceSlug, and idempotencyKey are already documented in the schema. The description reinforces the confirm requirement and idempotency retry semantics but adds no new syntax or format detail for those parameters, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact operation and its mechanism: "Freeze the draft as a new immutable version and point new enrollments at it," which is far more specific than the title "Publish a campaign." It implicitly distinguishes itself from draft-mutating and status-setting siblings by emphasizing immutability of published versions.

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

Usage Guidelines4/5

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

It gives a concrete precondition — "read the provider capabilities first" because publish is blocked when the provider cannot support a campaign requirement — which routes the agent to luca_campaigns_provider_capabilities. It also states the confirm:true gating requirement. It does not explicitly contrast publish with luca_campaigns_set_status or luca_campaigns_draft_update, leaving some sibling discrimination to inference.

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