NomaCMS MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Create Webhook

create_webhook

Create a webhook to receive notifications for content and authentication events. Specify event names and sources to trigger the webhook.

Instructions

Create a webhook for content and auth events

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": {
      "name": "<name>",
      "url": "<url>",
      "events": "<events>",
      "sources": "<sources>"
    },
    "name": "create_webhook"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Destination URL
`name`	Yes	Webhook display name
`events`	Yes	Event names
`secret`	No	Optional HMAC secret
`status`	No	Webhook active status
`payload`	No	Whether to include payload details
`sources`	Yes	Event sources (e.g. cms, api)
`description`	No	Optional description
`collection_ids`	No	Optional collection ID filter

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Jul 11, 2026

TDQS

C2.6/5.0

Behavior1/5

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

With no annotations provided, the description must fully disclose behavioral traits. It fails to mention side effects (e.g., immediate activation, test events), required permissions, or idempotency, leaving critical behavioral context unknown.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no fluff, but it sacrifices necessary detail for brevity. It earns its place by stating purpose but fails to cover other essential aspects.

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 tool's complexity (9 parameters, no annotations, no output schema), the description is insufficient. It does not explain webhook behavior, available events, return values, or prerequisites, making it incomplete for correct agent usage.

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?

Since schema coverage is 100%, the baseline is 3. The description adds no additional meaning to parameters beyond what the schema provides (e.g., 'Event names', 'Destination URL'). The brief mention of 'content and auth events' vaguely relates to the events parameter but does not clarify format or options.

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 verb 'Create' and resource 'webhook', and specifies 'for content and auth events', differentiating it from siblings like delete_webhook or update_webhook. However, it could be more specific about what 'content and auth events' entail.

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 (e.g., list_webhooks, update_webhook) and no prerequisites or exclusions. The agent lacks context for appropriate invocation.

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