Skip to main content
Glama

webhook_create

Register an outgoing webhook. The response carries the signing secret ONCE.

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": {
      "url": "<url>"
    },
    "name": "webhook_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
eventsNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one genuinely valuable non-obvious trait: the signing secret is returned exactly once, so the caller must persist it. It says nothing about permissions, URL validation, duplicate registration behavior, or what happens if events is omitted, so a mutation tool remains incompletely characterized.

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?

Two short sentences with zero filler, and the most operationally important fact (one-time secret) is placed where it cannot be missed. Nothing can be cut without losing information.

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?

A create/mutation tool with no annotations, no output schema, and three undocumented parameters should describe more than two sentences can: event filtering semantics and the consequences of failure are absent. The one-time-secret note is a good start but leaves the definition short of what an agent needs to invoke it confidently.

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?

Schema description coverage is 0% across all three parameters, so the description needed to compensate and does not. It never explains what url must be, what event names are accepted for events (no enums exist), whether events defaults to all events, or what description is for.

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?

"Register an outgoing webhook" states a specific verb (register) and resource (outgoing webhook), and the sibling names webhook_delete/webhook_list make the create-vs-delete/list distinction inferable. It stops short of explicitly contrasting with those siblings, so it lands at 4 rather than 5.

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 when-to-use guidance, no prerequisite or permission note, and no mention of alternatives such as listing existing webhooks first. The only implicit cue is the word "outgoing," which does not tell an agent under what conditions to register one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources