hello.new

Create webhook URL

create_webhook

Make a URL any service can call: Stripe, GitHub, a form, a cron job. Every request is stored for you to read with read_webhook_requests. Expires in 24 hours unless the user connected a hello.new account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_webhook"
  }
}

Input Schema

Name	Required	Description	Default
`note`	No	What the webhook is for, e.g. "Stripe test events".
`expires_in`	No	Seconds until the link expires. Default: 24 hours, or never on a hello.new account.

Output Schema

Name	Required	Description
`id`	Yes
`key`	Yes	For the other tools. Never give it out.
`url`	Yes	The link. Give it to people.
`claim_url`	No	Anonymous links: where the user can keep the link past 24 hours.
`stats_url`	Yes	A live dashboard of who opened the link, for the user.
`expires_at`	Yes	null: it never expires.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only cover the safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false). The description adds real behavioral value beyond them: request persistence ("Every request is stored") and the 24-hour expiry with its hello.new exception. It does not mention auth or rate-limit behavior, keeping it short of a 5.

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?

Three short sentences, zero filler. The core capability is front-loaded, followed by the reading path and the expiry caveat in priority order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the description covers the essentials an agent needs: what the tool produces, where the output surfaces (read_webhook_requests), and the lifetime constraint. Nothing material is missing.

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 100%, so both parameters are already documented in the schema, including the expiry default and the note field. The description's expiry statement merely echoes the schema, adding no new syntax or constraint detail. Baseline 3 applies.

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?

States a concrete verb+resource ("Make a URL") and clarifies the mechanism with examples ("Stripe, GitHub, a form, a cron job"). It is clearly distinguishable from create_upload_link by describing an inbound-callable endpoint, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives strong usage context: the URL is meant to be called by external services, and requests are consumed via read_webhook_requests, which routes the agent to the right companion tool. It stops short of stating when NOT to use this versus create_upload_link.

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

All hello.new tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?