Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete a webhook subscription

luca_webhooks_subscriptions_delete
DestructiveIdempotent

Delete an outbound webhook subscription. Terminal, idempotent soft delete: delivery history stays queryable and the subscription can never be resurrected.

Instructions

Delete an outbound webhook subscription. Terminal, idempotent soft delete: delivery history stays queryable and the subscription can never be resurrected.

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

Input Schema

NameRequiredDescriptionDefault
idYes
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint, but the description adds key non-obvious behavior: the delete is soft, delivery history remains queryable, and the subscription cannot be resurrected. Required scopes (webhooks:write, luca:full) are also disclosed. The 'Does not require idempotency' line is slightly confusing next to idempotentHint=true, but is best read as no idempotency key needed — not a contradiction.

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 behavioral warning in the first sentence, then structured metadata on separate lines. The scope/OAuth lines are boilerplate but compact and relevant; nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A mutation tool with strong annotation coverage, an output schema, and a description that supplies the crucial soft-delete/irreversibility context plus auth requirements. An agent has everything needed to call it safely; only an explicit alternative-path pointer is missing.

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% with workspaceId/workspaceSlug already described there; the description adds the meaningful detail that those params override a default workspace configured by the environment. The required 'id' has only a UUID pattern and no prose, but its role is obvious from the operation path.

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 ('Delete an outbound webhook subscription') and immediately clarifies that it is a soft delete with terminal semantics, distinguishing it from luca_webhooks_subscriptions_update/list. Also names the underlying endpoint, so an agent can map it precisely.

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

Usage Guidelines4/5

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

Gives strong usage context: 'terminal, idempotent soft delete' that 'can never be resurrected', which warns the agent this is irreversible at the logical level. It does not point at an alternative sibling (e.g., disable via update), so the when-not-to-use branch 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