Skip to main content
Glama

set_webhook_active

Pause or resume a webhook. (confirm-gated: previews until confirm: true)

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": {
      "id": "<id>",
      "isActive": "<isActive>"
    },
    "name": "set_webhook_active"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
isActiveYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-destructive, non-open-world mutation. The description adds genuinely new behavioral information: the call is confirm-gated and returns a preview until confirm is true, which materially changes how an agent must call it. It still omits side effects on deliveries already queued and whether the change is reversible.

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?

Two short sentences, front-loaded with the action and followed by the confirm gate, with no filler. Brevity is efficient rather than padded, though a few more words on the isActive mapping would have cost nothing.

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 no output schema, low schema description coverage, and two required parameters, the description should carry more weight than it does. It never explains what the preview returns, what a successful execution reports, or how the two undocumented required parameters behave.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% -- only confirm is documented, while id and isActive have no schema descriptions. The description does not say that id identifies the target webhook nor spell out that isActive=true resumes and isActive=false pauses, leaving the central boolean's polarity to inference.

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?

States a specific verb pair (pause or resume) against a specific resource (webhook), so an agent knows the effect immediately. Sibling operations like create_webhook or delete_webhook are distinguishable by verb alone, though the description never names them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the verb: call this to toggle a webhook between active and paused. The confirm-gating note gives a practical hint about the two-step invocation pattern, but there is no explicit when-to-use versus when-not guidance and no named alternative for permanent removal or recreation.

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.