Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Resume a broadcast billing paused

luca_broadcasts_resume
Destructive

Resume a billing-paused broadcast after a pack purchase or card update, sending remaining messages to live leads and skipping recipients already contacted.

Instructions

Resume a broadcast that billing paused, after buying a pack or updating the card. Sends the remaining messages to live leads; recipients already sent are left alone. A broadcast paused by hand is resumed with luca_broadcasts_retry instead.

Luca operation: POST /api/broadcasts/{id}/resume 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. 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_broadcasts_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
bodyNo
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
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.2

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: it discloses that remaining messages go to live leads, that already-sent recipients are skipped, that an Idempotency-Key is required or server-generated, that confirm: true is mandatory, and which OAuth scopes apply. The 'idempotentHint: false' annotation is consistent with the need for a caller-supplied key rather than contradicted by it.

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 core behavior and side effect in the first two sentences, then separates operational details into scannable lines. The Destructive and Idempotency-Key lines partially restate the confirm and idempotencyKey schema descriptions, which is mild redundancy rather than bloat.

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?

An output schema exists so return values need no explanation; the description covers everything else an agent needs for a destructive, idempotent-sensitive action — side effects, confirmation gate, retry key, auth scopes, and workspace scoping. Only body.reason's purpose is missing, which is minor for an optional free-text field.

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

Parameters4/5

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

Schema coverage is 67%, and the description supplies meaning for idempotencyKey, confirm, and the workspaceId/workspaceSlug override (default workspace), which the schema only partially documents. The nested body.reason parameter is never explained, leaving one gap.

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?

States a specific verb and resource ('Resume a broadcast that billing paused') plus the trigger condition, and explicitly separates it from the near-identical sibling luca_broadcasts_retry by naming the manually-paused case. An agent can pick between the two resume paths without opening either schema.

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

Usage Guidelines5/5

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

Gives the precondition for use ('after buying a pack or updating the card') and an explicit exclusion routing manually paused broadcasts to luca_broadcasts_retry. Both the when and the when-not are 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