Blujay MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Create a webhook

create_webhook

Registers an HTTPS endpoint to receive Blujay event notifications for messages, delivery updates, reactions, and calls, and returns a signing secret once.

Instructions

Send Blujay events (new messages, delivery updates, reactions, calls) to an HTTPS URL you run. Returns 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>",
      "event_types": "<event_types>"
    },
    "name": "create_webhook"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`event_types`	Yes	For example ["message.received", "message.delivered", "message.failed"].

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Nov 11, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare openWorldHint, non-idempotent and non-destructive, so this description earns credit only for what it adds: the HTTPS requirement and the important 'returns the signing secret once' fact, which warns the caller to persist the secret. It does not say what happens on duplicate URL registration (relevant given idempotentHint=false) or whether the endpoint must complete a handshake before events flow.

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 sentences, zero filler, with the core action and the key return-value caveat front-loaded. Every clause carries information.

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?

With no output schema, the description correctly notes the return value (signing secret, once). For a 2-parameter create tool this is nearly sufficient; gaps are duplicate-registration behavior and any verification/permission requirement, which matter given the non-idempotent annotation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% and the url parameter has no schema description, so the phrase 'HTTPS URL you run' usefully adds a constraint (must be HTTPS, must be caller-owned) beyond format=uri. event_types gains category meaning, though exact event strings are left to the schema's examples. This compensates for most of the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Send Blujay events ... to an HTTPS URL you run') and enumerates the event categories (messages, delivery updates, reactions, calls), which is far more specific than the title 'Create a webhook'. An agent can distinguish it from list_webhooks without opening either schema.

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?

Usage is only implied: the reader infers this is the registration step for a self-hosted endpoint. There is no explicit when-to-use vs. list_webhooks or update/delete alternatives, and no stated prerequisites such as account permissions or endpoint verification.

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