Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Send a test webhook event

webhookEndpoints_test
Destructive

Sends a realistic per-source sample event to a webhook endpoint for immediate synchronous delivery testing, so you can verify endpoint behavior in real time.

Instructions

Send a realistic per-source sample event to a webhook endpoint right now — a live, synchronous delivery test.

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

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.
sampleTypeNo
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

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is carried by structured data. The description earns credit for adding that the send is live and synchronous "right now", meaning the call blocks and produces real external side effects rather than a dry run. It does not disclose what a failure looks like, whether the test event is recorded in delivery history, or whether it counts against rate limits.

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?

A single front-loaded clause that wastes no words; "right now" and "live, synchronous" each carry meaning about timing and blocking behavior. The em-dash aside is slightly decorative but harmless.

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 synchronous delivery test whose entire purpose is observing the outcome, the definition says nothing about what the call returns (a delivery status? an HTTP response?) and there is no output schema to fill that gap. Annotations cover the mutation/safety angle, but the result-reporting aspect and the undocumented sampleType leave the picture incomplete for a 5-parameter write tool.

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?

The description contributes nothing about the five parameters beyond the phrase "per-source", which only hints at sampleType. Schema coverage is 60%: context, llm_model, and conversation_id are documented in the schema, but id and sampleType are bare. With a real coverage gap and no compensating explanation of valid sample sources or identifiers, the description leaves parameter meaning to the schema alone.

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?

"Send a realistic per-source sample event to a webhook endpoint" gives a specific verb (send) and resource (sample webhook event), which is clearly separable from the CRUD siblings (create/delete/get/list) and from webhookDeliveries_redeliver, which replays a real delivery rather than a sample. The title reinforces the same idea. It stops short of naming which sibling to prefer for verification workflows, but the action itself is unambiguous.

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

Usage Guidelines2/5

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

There is no explicit statement of when to use this versus checking endpoint state with webhookEndpoints_get, redelivering with webhookDeliveries_redeliver, or editing config first. The phrase "delivery test" implies the intent (verify an endpoint works), but no prerequisites, exclusions, or alternatives are stated. An agent must infer the whole selection rule.

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