Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update a webhook subscription

luca_webhooks_subscriptions_update
Destructive

Update an outbound webhook subscription.

Instructions

Update an outbound webhook subscription.

Luca operation: PATCH /api/webhook-subscriptions/{id} 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": {
      "id": "<id>"
    },
    "name": "luca_webhooks_subscriptions_update"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.1
    • addedInput schema / properties / body / properties / consumerMetadata / additionalProperties
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "object"
+    },
+    {
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "body"
-]New value: +[
+  "id"
+]
  2. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description reinforces this with a concrete consequence ('sends workspace events to an outside URL') plus the confirm: true rejection rule. It also adds genuinely non-obvious behavior: an Idempotency-Key is required and the server generates one if omitted, scopes are enumerated, and data sensitivity is marked 'redacted'. The idempotency note does not contradict idempotentHint=false — it describes the key mechanism that makes retries safe.

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?

The purpose is front-loaded in the first line, followed by short scannable lines for operation, scopes, idempotency, the destructive gate, and workspace override. It reads as a template with some boilerplate repetition of the confirm rationale, but no line is wasted.

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 not be explained, and annotations plus the description cover safety and auth. What's missing for a PATCH mutation with a nested body is the update semantics: which fields are patchable, whether omitted fields are left unchanged, and whether changing targetUrl or eventTypes affects in-flight deliveries or requires re-verification.

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 description coverage is 67%, and the description covers three of the six parameters (idempotencyKey, confirm, workspaceId/workspaceSlug) with meaningful context about defaults and server-side generation. The significant gap is the nested `body` object: the description never mentions that status, targetUrl, eventTypes, or consumerMetadata are the fields being updated, so the agent must read the schema to learn what can actually change.

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?

The description states a specific verb and resource ('Update an outbound webhook subscription') and anchors it to the concrete operation PATCH /api/webhook-subscriptions/{id}. The tool name plus this text makes it distinguishable from luca_webhooks_subscriptions_create/delete/list, though the description itself never explicitly contrasts with those siblings.

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?

It gives solid preconditions — required scopes (webhooks:write, luca:full), the mandatory confirm: true gate, and workspace override behavior — which tells the agent how to invoke it successfully. However, there is no guidance on when to choose this over luca_webhooks_subscriptions_create, delete, or test_delivery, and no statement of what a partial update does versus a full replace.

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