Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Update a webhook endpoint

webhookEndpoints_update

Update a webhook endpoint's description or toggle its status between active and disabled to control whether it receives events.

Instructions

Update a webhook endpoint's description or enable/disable it.

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_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
statusNo
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.
descriptionNo
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value by implying that only description and status are mutable (name/url are not), but it omits consequences of disabling (do deliveries stop? are queued events dropped?) and any permission requirements.

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?

One short, front-loaded sentence with zero padding or redundant restatement of the title. It is efficient, though the terseness leaves room for a clause about prerequisites or the effect of disabling.

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

Completeness3/5

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

For a mutation tool with annotations covering safety and no output schema, the definition is minimally adequate: it identifies the mutable fields but not the outcome of the mutation or required permissions. With 6 parameters at 50% schema coverage, an agent still lacks guidance on the operational side effects of disabling an endpoint.

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

Parameters4/5

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

Schema coverage is 50% (id, status, and description carry no schema descriptions), but the description compensates by mapping the ambiguous 'status' enum to plain-language enable/disable and by confirming 'description' is editable. It says nothing about the meta-parameters (context, llm_model, conversation_id), which are self-documented in the schema anyway.

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 concrete verb and resource ('Update a webhook endpoint') and narrows scope to exactly two mutable facets: description and enable/disable. An agent can distinguish this from create/delete/rotateSecret siblings by the operation itself, though the description never names or contrasts those alternatives.

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 only implied: an agent infers it should call this when changing a webhook's description or toggling its enabled state. There is no explicit 'use this instead of X' routing, no prerequisite (e.g. needing an existing endpoint id), and no note on when to prefer webhookEndpoints_rotateSecret or _test.

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