Skip to main content
Glama
Grist MCP Server
by nic01asFr

Create Webhook

create_webhook

Creates a Grist document webhook that sends notifications to a specified URL, optionally filtering by table and event types.

Instructions

Crée un webhook pour un document Grist.

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>",
      "url": "<url>"
    },
    "name": "create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL du webhook (où les notifications seront envoyées)
memoNoNote descriptive pour le webhook (optionnel)
doc_idYesL'ID du document
table_idNoID de la table à surveiller (optionnel, tous si non spécifié)
event_typesNoTypes d'événements à surveiller (optionnel, tous si non spécifié) Valeurs possibles: ["add", "update", "delete"]

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.2
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document"
    • addedInput schema / properties / event_types / description
      Added value: +"Types d'événements à surveiller (optionnel, tous si non spécifié)\n        Valeurs possibles: [\"add\", \"update\", \"delete\"]"
    • addedInput schema / properties / memo / description
      Added value: +"Note descriptive pour le webhook (optionnel)"
    • addedInput schema / properties / table_id / description
      Added value: +"ID de la table à surveiller (optionnel, tous si non spécifié)"
    • addedInput schema / properties / url / description
      Added value: +"URL du webhook (où les notifications seront envoyées)"
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutating operation. It does not disclose whether duplicate webhooks are rejected, whether the hook fires immediately or only on the specified events, what permissions are required, or whether creation is reversible — all relevant for a write tool.

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?

A single front-loaded sentence with zero filler, which is efficient. The terseness borders on under-specification rather than verbosity, but it is structurally clean.

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?

With five parameters, a required URL target, an output schema, and no annotations, the definition omits the operational context an agent needs: pairing with delete_webhook/modify_webhook, permission expectations, and webhook lifecycle behavior. The schema covers parameters, but the description does not cover the tool's behavior.

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%: every parameter, including url, doc_id, table_id, event_types (with allowed values), and memo, is documented in the schema itself. The description adds no extra meaning beyond that, 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 ('Crée un webhook') scoped to a Grist document, which is unambiguous. It does not, however, differentiate from siblings such as delete_webhook, modify_webhook, or clear_webhook_queue, so the agent gets no routing signal from the text.

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 create a webhook versus using modify_webhook or clear_webhook_queue, and no mention of preconditions such as existing document access or a reachable endpoint. The agent must infer everything from the tool name alone.

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