hello.new

Read webhook requests

read_webhook_requests

Read-only

Read the requests your webhook URL received: method, headers, query and body. Pass after (the last seq you saw) to get only newer ones, and wait (up to 20 seconds) to wait for the next request.

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": {
      "id": "<id>",
      "key": "<key>"
    },
    "name": "read_webhook_requests"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The link id, from the tool that made the link.
`key`	Yes	The link's key, from the tool that made the link.
`wait`	No	Seconds to wait for the next request. Default 0.
`after`	No	The last seq you saw: only newer requests come back. Default 0.

Output Schema

Name	Required	Description
`count`	Yes
`requests`	Yes
`expires_at`	Yes	null: it never expires.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it reveals the returned request parts, incremental polling via 'after', and a blocking wait of up to 20 seconds.

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 tightly written sentences with zero waste. The first sentence front-loads purpose and return contents; the second efficiently explains the two optional parameters. The minor 'wait ... to wait' repetition does not undermine the conciseness.

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?

For a simple read tool with 4 parameters, 2 required, full schema coverage, and an output schema, the description supplies all needed invocation context. Safety is covered by annotations, return shape by the output schema, and polling behavior by the description.

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 the schema already documents every parameter, including 'after' and 'wait'. The description reinforces these semantics (newer requests, up to 20 seconds) but adds no format details, edge cases, or defaults beyond what the schema provides; baseline 3 is appropriate.

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 specific verb 'read' and resource 'requests your webhook URL received', and enumerates the returned fields (method, headers, query, body). It does not explicitly differentiate itself from sibling tools like get_link_stats or list_files, so it falls short of 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 Guidelines3/5

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

The description implies usage by explaining incremental retrieval with 'after' and long-polling with 'wait', but it never explicitly states when to use this tool versus any alternative. Sibling tools are unrelated operations, so no clear alternative selection guidance is provided or needed.

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?