Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Replay a webhook event

luca_webhooks_events_replay
Destructive

Replay one canonical webhook event. Re-triggers subscribers' downstream automations.

Instructions

Replay one canonical webhook event. Re-triggers subscribers' downstream automations.

Luca operation: POST /api/webhook-subscriptions/events/{eventId}/replay Required scopes: webhooks:write Required OAuth scope: luca:full; 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": {
      "eventId": "<eventId>"
    },
    "name": "luca_webhooks_events_replay"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
eventIdYes
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. Changed1 schema field changedv0.4.1
    • changedInput schema / required
      Previous value: -[
-  "eventId",
-  "body"
-]New value: +[
+  "eventId"
+]
  2. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations by naming the actual downstream effect (subscribers' automations re-fire), the required scopes (webhooks:write, luca:full), the redacted data sensitivity, and the server-side idempotency-key generation fallback. It repeats the destructiveHint signal rather than refining it, and says nothing about partial-failure behavior or whether replays are themselves reversible.

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?

Purpose is front-loaded in the first line and the operational constraints follow in a compact block of labeled lines. The endpoint-path and scope metadata are boilerplate but cheap, and there is no redundant prose.

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 not be described; within that constraint the description covers auth scopes, the destructive confirm gate, idempotency strategy, and workspace override. That is enough for an agent to invoke this single-event replay correctly.

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?

At 67% schema coverage, the schema already documents confirm, idempotencyKey, workspaceId and workspaceSlug – the description largely restates those same points. eventId is required yet only constrained by minLength, and the nested body.subscriptionId is undocumented in both schema and description, leaving its purpose 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 and resource ('Replay one canonical webhook event') plus the consequence ('Re-triggers subscribers' downstream automations'). The word 'one' implicitly separates it from bulk replay, but the sibling luca_webhooks_events_bulk_replay is never named, so the differentiation must be inferred.

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?

Gives concrete preconditions for invocation (must pass confirm: true, idempotencyKey for safe retries) but never states when to choose this over bulk_replay or deliveries_replay. Usage is implied rather than routed.

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