Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a campaign

luca_campaigns_create

Create a campaign draft. Body requires name and may include graph.

Instructions

Create a campaign draft. Body requires name and may include graph.

Luca operation: POST /api/campaigns 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. 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_campaigns_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

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.8/5.0
Behavior5/5

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

Goes well beyond the annotations by naming the HTTP operation, the required OAuth scopes, the redaction sensitivity level, and the idempotency contract including server-side key generation. The idempotencyKey guidance complements rather than contradicts idempotentHint=false, clarifying that retries are only safe when a key is supplied.

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 requirement, followed by short operational lines. The scope/auth lines are somewhat terse but each carries distinct information; no filler sentences.

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 no explanation, and auth/idempotency are covered. However, for a tool whose payload is a deeply nested campaign graph with required version/startNodeId/nodes, the description gives no guidance on constructing that body, leaving the highest-risk part of the call unexplained.

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 top-level parameters are already documented and the description largely restates workspace override and idempotency behavior. The far more complex nested body.graph (16 node types, edges, knowledge, qualification) has no field-level descriptions anywhere, and 'may include graph' does nothing to explain it.

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 ('Create a campaign draft') and the 'draft' qualifier implicitly separates it from publish/set_status siblings. It does not explicitly name the alternative to use when the agent wants a live or duplicated campaign, so sibling differentiation is only partial.

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 description gives operational guidance (workspace override, idempotencyKey, required scopes) but never says when to prefer this over luca_campaigns_duplicate, luca_campaigns_generate, or luca_campaigns_publish, nor any precondition such as needing a workspace context first. Usage is implied rather than stated.

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