Skip to main content
Glama
Grist MCP Server
by nic01asFr

Modify Webhook

modify_webhook

Update an existing Grist webhook by changing its URL, watched table, event types, active state, or memo note. Specify document and webhook IDs to apply the modifications.

Instructions

Modifie un webhook existant.

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": "modify_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoNouvelle URL du webhook (optionnel)
memoNoNouvelle note descriptive (optionnel)
activeNoÉtat d'activation du webhook (optionnel)
doc_idYesL'ID du document
table_idNoNouvel ID de table à surveiller (optionnel)
webhook_idYesL'ID du webhook à modifier
event_typesNoNouveaux types d'événements à surveiller (optionnel)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.2.2
    • addedInput schema / properties / active / description
      Added value: +"État d'activation du webhook (optionnel)"
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document"
    • addedInput schema / properties / event_types / description
      Added value: +"Nouveaux types d'événements à surveiller (optionnel)"
    • addedInput schema / properties / memo / description
      Added value: +"Nouvelle note descriptive (optionnel)"
    • addedInput schema / properties / table_id / description
      Added value: +"Nouvel ID de table à surveiller (optionnel)"
    • addedInput schema / properties / url / description
      Added value: +"Nouvelle URL du webhook (optionnel)"
    • addedInput schema / properties / webhook_id / description
      Added value: +"L'ID du webhook à modifier"
  2. First observedv0.1.0

TDQS

C2.2/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 burden, and it discloses essentially nothing beyond the fact that a mutation occurs. It does not say whether the update is partial (leaving unspecified fields untouched), whether changes are reversible, what permissions are needed, or whether the webhook is re-registered/validated on URL change.

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 sentence is free of padding but is severely under-specified for a seven-parameter mutation tool; brevity here comes at the cost of usefulness rather than from efficient wording.

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, which relieves the description of explaining return values, but with no annotations and a mutation of seven parameters the description should at minimum state partial-update behavior and permission requirements. It instead says nothing an agent could not infer from the name alone.

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%, so every one of the seven parameters is already documented in the schema, establishing the baseline of 3. The description adds no meaning beyond the schema — for example, it does not explain partial-update semantics when url/active/event_types are left null.

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?

"Modifie un webhook existant" restates the tool name (modify_webhook) almost verbatim, supplying only the qualifier that the webhook must already exist. It names no updatable fields and does not distinguish this tool from siblings such as create_webhook or delete_webhook beyond the generic verb.

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 when-to-use guidance, no mention of prerequisites (permissions, ownership of the webhook), and no routing to alternatives. The single word "existant" is the only implicit hint, and it is too vague to count as usage guidance.

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