Skip to main content
Glama

Webhooks Create

webhooks_create

Creates a new webhook for an organisation by posting the full JSON:API document unchanged to the organisation's webhooks endpoint.

Instructions

Create new webhook. POST /organisations/{organisationId}/webhooks

payload is the full JSON:API document (data/attributes), passed through unchanged.

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": {
      "organisation_id": "<organisation_id>",
      "payload": "<payload>"
    },
    "name": "webhooks_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose one useful trait – the payload is a JSON:API document passed through unchanged, implying no server-side normalization – but it says nothing about required permissions, duplicate-webhook behavior, error responses, or what is returned on creation.

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?

Two short sentences, front-loaded with the action and endpoint, followed by the key payload note. The endpoint line partially repeats the verb but remains informative; there is no padding.

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 two-parameter create tool with no output schema and no annotations, the description covers invocation adequately (organisation id in the path, JSON:API payload shape). It is incomplete regarding the response body – notably whether a webhook id is returned, which an agent would likely need – and regarding failure modes.

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 description coverage is 0%, so the description must compensate, and it does for the harder parameter: 'payload' is explained as a full JSON:API data/attributes document passed through untouched, which is meaningful beyond the opaque 'object' type in the schema. 'organisation_id' is only reflected via the URL template and is not otherwise clarified.

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 gives a specific verb and resource ('Create new webhook') plus the concrete endpoint POST /organisations/{organisationId}/webhooks, which unambiguously separates it from the sibling read/delete webhook operations. It stops short of explicitly noting scope boundaries (e.g. that it does not list or test webhooks), so a 4 rather than a 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 or when-not-to-use guidance, no mention of prerequisites such as an existing endpoint URL or authentication, and no reference to alternatives like webhooks_index or webhooks_show. The usage is only implied by the verb 'Create'.

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