Skip to main content
Glama

server_get_webhook

Retrieve webhook details for a specific server by providing server and webhook IDs to monitor or manage integration endpoints.

Instructions

Get details for a specific webhook

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
webhook_idYesWebhook ID

Implementation Reference

  • The server_get_webhook tool implementation including registration and handler logic.
    server.tool(
      "server_get_webhook",
      "Get details for a specific webhook",
      {
        server_id: z.string().describe("Server ID or UUID"),
        webhook_id: z.string().describe("Webhook ID"),
      },
      async ({ server_id, webhook_id }) => {
        try {
          const data = await client.get(
            `/servers/${server_id}/webhooks/${webhook_id}`
          );
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: "text", text: `Error: ${msg}` }], isError: true };
        }
      }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get details'), which implies it's non-destructive, but doesn't address other important aspects like authentication requirements, error conditions (e.g., what happens if the webhook doesn't exist), rate limits, or the format of returned details. The description is too minimal for a tool that likely involves server access.

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?

The description is a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a simple lookup tool and front-loads the core purpose immediately.

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

Completeness2/5

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

Given the complexity (a server/webhook management tool with no annotations and no output schema), the description is incomplete. It doesn't explain what 'details' are returned, potential side effects, or error handling. For a tool that likely interacts with a server system, more context about the operation's behavior and output would be helpful.

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?

The input schema has 100% description coverage, with both parameters ('server_id' and 'webhook_id') clearly documented in the schema itself. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline of 3 for adequate coverage when the schema does the heavy lifting.

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 clearly states the action ('Get details') and resource ('for a specific webhook'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'server_list_webhooks' by focusing on a single webhook rather than listing multiple. However, it doesn't specify what details are retrieved, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'server_list_webhooks' or 'server_update_webhook'. It doesn't mention prerequisites (e.g., needing the webhook ID from a list operation) or contextual constraints, leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HadiCherkaoui/crafty-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server