Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Create a webhook endpoint

webhookEndpoints_create

Creates a delivery target for monitor events: use an HTTPS URL for webhooks or a hosted test inbox when no endpoint exists. Store the returned signing secret immediately.

Instructions

Create a delivery target for monitor events. kind=http requires a public HTTPS url; kind=sink is a hosted test inbox with no url. The signing secret is returned once — store it now.

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": {
      "kind": "<kind>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "webhookEndpoints_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
kindYes
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.9/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, non-destructive, non-idempotent mutation, and the description adds the behavior an agent cannot get from those hints: the signing secret is returned exactly once and must be stored immediately. That is a meaningful operational warning about an irreversible consequence (a lost secret). It does not describe rate limits or error behavior, but for a create call this is solid added value.

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 short sentences with zero filler: purpose first, mode constraints second, the one-time secret warning last. The most consequential detail (store the secret now) is positioned where it will be read rather than 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?

With no output schema, the description carries some of the return-value burden and does so for the critical field (the signing secret). The other required parameters are covered by schema descriptions, and the kind/url interplay is resolved. Minor gaps remain around what identifier the created endpoint returns and how conversation_id sequencing interacts with creation, though the schema addresses the latter.

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 only 50%, so the description has to compensate, and it does for the most important case: it explains the url parameter's conditional relationship to kind (required for http, irrelevant for sink), which the schema's flat property list does not convey. The remaining parameters (context, llm_model, conversation_id) are self-documenting in the schema, and the description parameter is undocumented but obvious by name.

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 opens with a specific verb and resource: 'Create a delivery target for monitor events,' which an agent can immediately map to the create-vs-get/list/update/rotateSecret siblings. It never explicitly names a sibling, so differentiation rests on the verb rather than an explicit contrast.

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 kind=http vs kind=sink breakdown gives useful conditional guidance on which creation mode to pick, including the requirement of a public HTTPS url for http. There is no explicit statement of when to choose this tool over webhookEndpoints_update or webhookEndpoints_test, so usage is implied rather than spelled out.

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