Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a webhook subscription

luca_webhooks_subscriptions_create
Destructive

Create an outbound webhook subscription.

Instructions

Create an outbound webhook subscription.

Luca operation: POST /api/webhook-subscriptions Required scopes: webhooks:write Required OAuth scope: luca:full; data sensitivity: redacted Does not require idempotency. 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": {
      "body": "<body>"
    },
    "name": "luca_webhooks_subscriptions_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
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.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
+    }
+  ]
+}
  2. First observedv0.4.0

TDQS

A4.7/5.0
Behavior4/5

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

While the annotations mark it as destructive, the description adds critical behavioral context by specifying *how* the destruction is governed (the `confirm: true` gate). It also clarifies operational constraints like scoping and required OAuth scopes, providing richer behavioral context than the structured metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The information is dense but highly structured. It front-loads the core purpose, follows with required operational parameters (scopes), and concludes with critical safety and contextual requirements, maximizing efficiency.

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?

Given this is a complex, destructive API call, the definition is comprehensive. It covers the endpoint, required permissions, safety gates, and deployment/scoping context (default workspace vs. override), leaving virtually no operational uncertainty for the agent.

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?

The description provides meaning beyond the schema by detailing the operational inputs (`confirm: true`) and the purpose of the scoping parameters (`workspaceId` or `workspaceSlug` override). This compensates for the 75% schema coverage by clarifying necessary operational logic.

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 clearly states the action ('Create an outbound webhook subscription') and provides the associated REST operation (`POST /api/webhook-subscriptions`). This is specific and leaves no ambiguity regarding its function relative to sibling tools.

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?

The description sets multiple critical usage rules: it defines the necessary scopes, explicitly warns of a 'real-world side effect,' and dictates a non-negotiable usage pattern: 'You must pass confirm: true.' This level of instruction is exceptional for ensuring safe and correct invocation.

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