LivePage · 活页

Check published appearance

preview_version

Read-onlyIdempotent

Returns an interactive preview link (interactive_url) to the real SPACE viewer, open for 60 minutes. Screenshots are disabled on this server: no images are returned and screenshot_status is disabled. Hand interactive_url to the requesting user: it needs no login and shows desktop or mobile (as in WeChat), or both side by side, and fills the screen when opened on a phone. Default visitor audience never includes speaker notes. Read-only: does not publish, record visits, submit feedback, edit access or join live presenter rooms. Device emulation does not verify real phones, WeChat or cross-device remote control. Pass embed_origin to also get embed.url: an embed link only that parent origin (a platform first-party origin such as https://claudefleet.24haowan.com, or one on the workspace embed allowlist) may frame, read-only, no login, no visit tracking, no feedback or form submissions, valid at most 60 minutes; call again to refresh. Preview links grant temporary access to one version; share only with the requesting user. Keywords: publish · web page · webpage · link · share · share to WeChat · WeChat link · html · pdf · markdown · upload · LivePage · proposal.

Input Schema

Name	Required	Description	Default
`page`	No
`panel`	No		document
`theme`	No		default
`wait_ms`	No
`audience`	No		visitor
`viewports`	No
`version_id`	Yes
`embed_origin`	No	To embed this version in another page, the parent origin (such as https://claudefleet.24haowan.com); platform first-party origins are allowed by default, any other origin must already be on the workspace embed allowlist. Returns embed.url (read-only, no login, at most 60 minutes, only that origin may frame it).
`embed_renewable`	No	For an authenticated internal studio: also return embed.renewal (read-only, exact version/origin, max 7 days or token expiry). Keep renewal.key on the trusted server; never expose it in a page URL. No publishing or editing rights.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

addedInput schema / properties / embed_renewable

Added value: +{
+  "description": "For an authenticated internal studio: also return embed.renewal (read-only, exact version/origin, max 7 days or token expiry). Keep renewal.key on the trusted server; never expose it in a page URL. No publishing or editing rights.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / embed_origin / description

Previous value: -"To embed this version in another page, the parent origin (such as https://ccquota.24haowan.com); it must already be on the workspace embed allowlist. Returns embed.url (read-only, no login, at most 60 minutes, only that origin may frame it)."New value: +"To embed this version in another page, the parent origin (such as https://claudefleet.24haowan.com); platform first-party origins are allowed by default, any other origin must already be on the workspace embed allowlist. Returns embed.url (read-only, no login, at most 60 minutes, only that origin may frame it)."

Changed1 schema field changedOct 21, 2026

addedInput schema / properties / embed_origin

Added value: +{
+  "description": "To embed this version in another page, the parent origin (such as https://ccquota.24haowan.com); it must already be on the workspace embed allowlist. Returns embed.url (read-only, no login, at most 60 minutes, only that origin may frame it).",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

First observedOct 6, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the annotations with behavior an agent could not otherwise know: 60-minute expiry, screenshots disabled and screenshot_status disabled, no login required, visitor audience never includes speaker notes, device emulation does not verify real phones/WeChat, embed links are origin-locked to allowlisted parents and expire, and renewal keys must stay server-side. This is exactly the extra context annotations can't carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, which is good, but the body is a dense run-on of chained clauses and the trailing 'Keywords: publish · web page · ...' list is search-stuffing that adds noise rather than agent-relevant meaning. Several constraints are repeated (60 minutes appears twice, no login twice).

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 names the fields returned (interactive_url, embed.url, screenshot_status, embed.renewal) and covers security/expiry constraints, so an agent can call and hand off the result safely. The remaining gap is the unexplained page/panel/theme/wait_ms parameters, which leave preview composition ambiguous.

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 only 22% across 9 parameters, so the description must compensate. It does cover the consequential ones — audience (visitor default, no speaker notes), viewports (desktop/mobile/both side by side, fills a phone screen), embed_origin and embed_renewable — but page, panel, theme, wait_ms and version_id get no semantics at all.

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 opening sentence states a specific verb and artifact: returns an interactive preview link to the real SPACE viewer, valid 60 minutes. The explicit 'Read-only: does not publish, record visits...' clause separates it from write-side siblings such as publish_version and push_to_wechat without needing to open their schemas.

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 concrete operating instructions: 'Hand interactive_url to the requesting user', 'Pass embed_origin to also get embed.url', 'call again to refresh', and 'share only with the requesting user'. It also enumerates what it does not do (no publishing, no feedback, no presenter rooms). It never names a sibling alternative by name, which keeps it below a 5.

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

All LivePage · 活页 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?