@createworker/mcp

Official

Overview Schema Source Related Servers Discussions Admin

Register an event webhook

webhook_register

Subscribe a URL to CreateWorker events (task.completed, proposal.needs_approval) and receive a one-time signing secret for verification.

Instructions

Subscribe a URL to CreateWorker events (task.completed, proposal.needs_approval, …). Returns a 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>",
      "events": "<events>"
    },
    "name": "webhook_register"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`events`	Yes
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 30, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses that a signing secret is returned only once, but does not mention authentication, rate limits, or error handling.

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?

The description is one sentence with essential information, front-loaded. The ellipsis after events list is slightly unclear but overall concise.

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?

With no output schema or annotations, the description is insufficiently complete: it omits parameter details, error conditions, and full return value description.

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 coverage is 0%, so description must compensate. It hints at 'url' and 'events' parameters but does not explain the 'description' parameter or provide formatting details.

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?

The description clearly states the tool registers a webhook URL for CreateWorker events, with specific examples. It distinguishes itself from sibling tools like connection_create_webhook by focusing on event subscriptions.

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?

The description implies the tool is for subscribing to worker events, but does not explicitly state when to use it over alternatives, nor provides when-not-to-use guidance.

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