Skip to main content
Glama
Grist MCP Server
by nic01asFr

Delete Webhook

delete_webhook

Removes a webhook from a Grist document by specifying the document ID and webhook ID.

Instructions

Supprime un 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": {
      "doc_id": "<doc_id>",
      "webhook_id": "<webhook_id>"
    },
    "name": "delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
webhook_idYesL'ID du webhook à supprimer

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.2
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document"
    • addedInput schema / properties / webhook_id / description
      Added value: +"L'ID du webhook à supprimer"
  2. First observedv0.1.0

TDQS

C2/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure and delivers none of it. It does not state that the deletion is destructive and irreversible, what permissions are required, whether queued events or delivery history are dropped, or whether deleting a nonexistent webhook errors or succeeds silently.

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?

The single four-word sentence contains no wasted words, but it is under-specified rather than concise. Given that this is a destructive mutation with two required parameters, a description this size leaves the agent with nothing actionable.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. However, for a destructive, unannotated mutation tool, the definition is missing the essentials: irreversibility, permission requirements, and side effects on queued webhooks or existing deliveries.

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 description coverage is 100%: doc_id ("L'ID du document") and webhook_id ("L'ID du webhook à supprimer") are both documented in the schema. The description adds no meaning beyond this, so the baseline of 3 applies, though it also does not clarify the parent-child relationship between doc_id and webhook_id.

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?

"Supprime un webhook" is a verb-plus-resource, but it conveys nothing beyond what the tool name delete_webhook and the title Delete Webhook already state. There is no scope information (which webhook, owned by whom, whether queued deliveries are affected) and no differentiation from siblings such as clear_webhook_queue or modify_webhook.

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?

No when-to-use or when-not-to-use guidance at all. An agent gets no signal about how this differs from clear_webhook_queue (clearing pending deliveries) or modify_webhook, nor any prerequisite such as needing to know the doc_id first.

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