Skip to main content
Glama

Replace a webhook's signing secret

rotate_webhook_secret
Destructive

Makes a new signing secret for a webhook endpoint and returns it once (store it now): deliveries from now on are signed with it, and the old secret stops working at once, so update the receiving side right away. Use it when the old secret may have leaked.

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": {
      "workspace_id": "<workspace_id>",
      "webhook_id": "<webhook_id>"
    },
    "name": "rotate_webhook_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhook_idYes
workspace_idYesWorkspace id from list_workspaces

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description goes beyond that with details annotations cannot carry: the secret is returned exactly once and must be stored immediately, deliveries are signed with the new secret from that point, and the old secret stops working at once. That immediate-invalidation consequence is precisely what an agent needs before invoking a destructive rotation.

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?

Two sentences, no filler: the operation and its return-once caveat come first, the invalidation consequence second, and the usage trigger last. The parenthetical 'store it now' earns its place as an actionable warning.

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

Completeness4/5

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

With no output schema, the description correctly states the return value (the new secret, delivered once) and the side effect on existing deliveries, which is the essential context for this mutation. The remaining gap is identifying the target webhook — neither the description nor the schema explains the webhook_id parameter.

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 description coverage is only 50% — workspace_id points at list_workspaces, but webhook_id has no description in the schema and none in the description text either. The description never mentions that two identifiers are required or how to obtain the webhook id, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete operation on a concrete resource — 'Makes a new signing secret for a webhook endpoint' — and states what it hands back ('returns it once'). That is clearly distinct from create_webhook or delete_webhook, so an agent can pick this tool without opening any schema.

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

Usage Guidelines4/5

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

It gives an explicit trigger condition: 'Use it when the old secret may have leaked.' What's missing is the flip side — when not to rotate (e.g. routine setup, or if a create/regenerate sibling already covers the case) — so the guidance is clear but not exhaustive.

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