Skip to main content
Glama
benswel

QR for Agent

by benswel
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

delete_webhook

Remove a webhook endpoint from the QR for Agent MCP server to stop event reception and delete associated delivery logs.

Instructions

Delete a webhook endpoint and all its delivery logs. The endpoint will stop receiving events immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
webhook_idYesThe ID of the webhook to delete. Use list_webhooks to find IDs.

Implementation Reference

  • packages/mcp/src/tools.ts:694-696 (handler)
    The tool handler for delete_webhook in the MCP tool definitions file. It makes a DELETE request to the /api/webhooks/{webhook_id} endpoint.
    handler: async (input: { webhook_id: number }) => {
  return apiRequest(`/api/webhooks/${input.webhook_id}`, { method: "DELETE" });
},
  • packages/mcp/src/tools.ts:686-696 (registration)
    The registration of the delete_webhook tool within the tools configuration object.
    delete_webhook: {
  description:
    "Delete a webhook endpoint and all its delivery logs. The endpoint will stop receiving events immediately.",
  inputSchema: z.object({
    webhook_id: z
      .number()
      .describe("The ID of the webhook to delete. Use list_webhooks to find IDs."),
  }),
  handler: async (input: { webhook_id: number }) => {
    return apiRequest(`/api/webhooks/${input.webhook_id}`, { method: "DELETE" });
  },

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It effectively discloses destructive traits: deletion of delivery logs alongside the endpoint and immediate effect timing. It could improve by stating whether the action is irreversible or requires specific permissions.

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?

Two sentences with zero waste. The first states the action and scope; the second states the immediate behavioral consequence. Information is front-loaded and every clause earns its place.

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?

For a single-parameter destructive operation without output schema, the description adequately covers the primary effect and side effects (log deletion). It could mention irreversibility or return value structure to be fully complete.

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?

The input schema has 100% description coverage for the webhook_id parameter, including a reference to list_webhooks. The description adds no parameter-specific semantics, which aligns with the baseline score of 3 for high-coverage schemas.

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 uses the specific verb 'Delete' with the resource 'webhook endpoint' and clarifies scope by mentioning 'all its delivery logs'. It clearly distinguishes from siblings like create_webhook, list_webhooks, and QR code tools.

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?

The description provides clear behavioral context ('The endpoint will stop receiving events immediately'), implying when to use it (when immediate cessation is needed). However, it lacks explicit comparison to alternatives or exclusion criteria (e.g., when to update vs delete).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/benswel/qr-agent-core'

If you have feedback or need assistance with the MCP directory API, please join our Discord server