hello.new

Share a page

share_page

Publish Markdown as a web page anyone with the link can read: a report, a summary, a draft for review. Give people the url. Expires in 24 hours unless the user connected a hello.new account.

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": {
      "content": "<content>"
    },
    "name": "share_page"
  }
}

Input Schema

Name	Required	Description
`title`	No	Shown above the page.
`content`	Yes	The page, in Markdown. At most 256 KB.
`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

A3.7/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false), and the description goes beyond them by disclosing the key behavioral trait: the link expires in 24 hours unless a hello.new account is connected, plus that the page is publicly readable by anyone with the URL. It does not address permissions, rate limits, or whether content is retained after expiry.

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?

Front-loaded with the core action and kept to two compact sentences with no filler. It could be tightened slightly by folding the expiry clause more directly into the main statement.

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 an output schema present, return values need no explanation, and the description covers the essential behavior (public visibility, 24-hour expiry). The main gap is the absence of routing guidance versus create_upload_link.

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 coverage is 100%, so the schema already documents title, content, and expires_in. The description only reinforces the expiry default, adding marginal value beyond the schema's own description of the same behavior.

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 and resource: publishing Markdown as a shareable web page, with concrete examples (report, summary, draft). It distinguishes itself well from most siblings, though it does not explicitly contrast with create_upload_link, the nearest neighbor for producing a shareable link.

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 examples and 'anyone with the link can read' imply the usage context, but there is no explicit when-to-use routing against create_upload_link or any statement of exclusions. Usage is inferable but not spelled out.

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?