Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get a webhook endpoint

webhookEndpoints_get
Read-onlyIdempotent

Retrieve a single webhook endpoint by ID to inspect its configuration while excluding secret material.

Instructions

Get one webhook endpoint by id (secret material never included).

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

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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The one genuine addition is that secret material is never included in the response, which is useful return-content context. It says nothing about behavior for unknown or deleted ids, which for a by-id getter is a notable gap.

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 sentence with zero filler, and the parenthetical caveat is placed after the core statement where it belongs. It is arguably too sparse rather than too long, but nothing is wasted.

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 simple single-record getter with strong annotations and no output schema, the description covers what the tool does and one important return-value nuance (no secrets). The remaining omission is error behavior for a missing id, which is minor for a read-only lookup.

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%, and the schema itself documents context, llm_model, and conversation_id thoroughly, so the baseline of 3 applies. The description only restates that lookup is by id and adds no format, validation, or meaning beyond the schema.

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 states a specific verb and resource ('Get one webhook endpoint by id') and scopes it to a single record, which implicitly separates it from webhookEndpoints_list. It stops short of naming a sibling or contrasting behavior explicitly, so it is clear but not fully differentiating.

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?

'by id' implies the tool is for fetching a known endpoint, whereas the list sibling would be for discovery, but the guidance is only implied. There is no statement of when not to use it, nor any pointer to update/rotateSecret/delete operations on the same resource.

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