Skip to main content
Glama
Sign In
BlindPay MCP Server

BlindPay MCP Server

by blindpaylabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete Instances Webhook Endpoints By Id

DeleteV1InstancesWebhookEndpointsById
DestructiveIdempotent

Deletes a webhook endpoint from a BlindPay instance by endpoint ID, stopping event delivery to that URL. Use it to remove obsolete or misconfigured webhook receivers.

Instructions

Remove Webhook

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": {
      "instance_id": "<instance_id>",
      "id": "<id>"
    },
    "name": "DeleteV1InstancesWebhookEndpointsById"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
instance_idYes
Idempotency-KeyNoOptional key to safely retry this request without performing the action twice. Retrying with the same key and an identical body replays the original response; reusing a key with a different body returns an error. Keys are kept for 24 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.3

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is known without the description. The description adds nothing beyond that — no note on irreversibility, cascade effects, or whether the endpoint stops receiving events immediately.

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

Conciseness2/5

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

Two words is under-specification rather than conciseness. There is no wasted text, but the definition is far too thin to earn its place as the sole prose guidance for a destructive mutation.

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

Completeness1/5

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

For a destructive, open-world delete operation with no output schema and two undocumented required parameters, the description provides nothing an agent needs: not the target resource shape, not the effect scope, not error or retry behavior.

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

Parameters2/5

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

Schema description coverage is only 33%: the required id and instance_id properties carry no description in the schema, and the description supplies no meaning for them either. Only Idempotency-Key is documented, and that documentation lives entirely in the schema, not the description, so the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Remove Webhook" only restates the tool name (Delete Instances Webhook Endpoints By Id) in compressed form. It conveys the verb+resource but drops the instance scoping and adds no detail distinguishing this from the sibling GetV1InstancesWebhookEndpoints / PostV1InstancesWebhookEndpoints endpoints.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives, no prerequisites, and no warning about what happens to in-flight webhook deliveries. The agent must infer everything from the tool name.

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