Skip to main content
Glama

rotate_webhook_secret

Destructive

Rotate the signing secret for a webhook. The new secret will only be shown once. The old secret keeps signing for 24 hours: every delivery then carries X-OmniSocials-Signature (new secret) and X-OmniSocials-Signature-Previous (old secret, same format), so the receiving endpoint keeps accepting deliveries while it switches to the new secret.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe webhook ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds genuinely new behavioral facts: the new secret is shown only once, the old secret remains valid for exactly 24 hours, and both X-OmniSocials-Signature and X-OmniSocials-Signature-Previous are sent during the overlap. This is the kind of irreversibility and migration detail an agent cannot get from structured fields.

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?

Three tight sentences with the core action and the irreversible consequence front-loaded, followed by the rollover mechanics. No redundant wording and nothing that could be cut without losing information.

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

Completeness5/5

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

For a mutation tool with no output schema, the description covers what matters: that the returned secret is single-display, and how existing traffic keeps working during the transition. An agent can call this and advise the caller correctly without additional documentation.

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?

There is a single required parameter with 100% schema description coverage, so the schema already fully documents 'id'. The description adds no further meaning about the identifier or how to obtain it, which is acceptable at the baseline for a one-param tool.

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?

A specific verb+resource ('Rotate the signing secret for a webhook') that an agent can distinguish from update_webhook, get_webhook, or delete_webhook by intent. It does not explicitly name those siblings, so the differentiation is inferential rather than stated.

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?

The rotation scenario is implied clearly enough (you need a new signing secret), and the 24-hour dual-signing window gives useful operational context. However, there is no explicit when-to-use vs. update_webhook, and no stated prerequisites such as required role or permission.

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