Skip to main content
Glama

Удаление вебхука

delete_quiz_webhook
Destructive

Удаляет вебхук опроса вместе с его заголовками и журналом отправок.

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": {
      "quiz_id": "<quiz_id>",
      "webhook_id": "<webhook_id>"
    },
    "name": "delete_quiz_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
webhook_idYesID вебхука (из get_quiz_webhooks).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not obligated to establish that this is a mutation. It earns credit for disclosing the cascade — headers and the send log are removed too — which is real behavioral information not present in the annotations or schema. It stops short of stating irreversibility or required 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?

A single sentence with zero filler, and the cascade information is packed into the same clause rather than padded out. Nothing could be removed without losing information.

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?

For a destructive two-parameter tool with no output schema, the cascade disclosure plus the annotations cover the essentials. Missing is whether the deletion is permanent, whether webhook_id must belong to quiz_id, and what the caller gets back, which leaves a gap for an irreversible operation.

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 coverage is 100% and the webhook_id property already points to get_quiz_webhooks as the source. The description adds nothing about parameter meaning or the relationship between quiz_id and webhook_id, so the baseline 3 applies.

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 (deletes the quiz webhook) and adds the scope of the deletion — headers and submission log. It is unambiguous about what is removed, though it does not explicitly contrast itself with the toggle/update siblings.

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 guidance on when to delete versus when to use toggle_quiz_webhook to merely disable, and no prerequisites or warnings are stated. The agent must infer the choice from sibling names alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources