Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Rotate a webhook endpoint secret

webhookEndpoints_rotateSecret
Destructive

Rotate a webhook signing secret with a 24-hour overlap so the old secret stays valid until expiration; the new secret is returned once.

Instructions

Rotate the signing secret with a 24h overlap window — the old secret keeps working until it expires. The new secret is returned once.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "webhookEndpoints_rotateSecret"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior5/5

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

The annotations already flag destructive=true and non-idempotent, and the description adds high-value behavior beyond them: a 24h overlap during which the old secret still works, and that the new secret is returned only once. The 'returned once' disclosure is especially important given there is no output schema, since it tells the agent the value is irrecoverable if dropped.

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 tight sentences with the operational constraint (overlap window) front-loaded and the return caveat immediately after. Nothing is wasted or buried.

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?

For a destructive, non-idempotent mutation with no output schema, the description supplies the essential behavioral facts: overlap duration, old-secret validity, and one-time return of the new secret. It stops short of naming required permissions or error behavior, which keeps it from a full 5.

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 coverage is 75%, with the three required params (id, context, llm_model) and conversation_id already documented in the schema. The description contributes nothing about parameter meaning, so it does not compensate for the remaining documentation gap. This is the baseline for schema that largely speaks for itself.

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 gives a specific verb and object ("Rotate the signing secret"), which is unambiguous. It does not explicitly contrast with sibling tools like webhookEndpoints_update, so an agent must infer that update handles other settings while this one only rotates the secret.

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 — you call this when you need to rotate a secret — but there is no explicit when-to-use or when-not guidance, and no mention of prerequisites or alternatives such as webhookEndpoints_update. The overlap-window detail hints at the operational context but does not route the agent between tools.

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

Deploy Server

Other Tools