Create Web Page

Preview Landing Page

page.preview

Read-onlyIdempotent

Return the current preview URL for a page.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pageId`	Yes	The pageId returned by page.create.
`editToken`	No	Required for anonymous demo pages. Use the editToken returned by page.create.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`slug`	Yes
`title`	Yes
`pageId`	Yes
`status`	Yes
`actions`	Yes
`content`	No
`claimUrl`	Yes
`editToken`	Yes
`expiresAt`	Yes
`isClaimed`	Yes
`nextSteps`	No	Enrichment hints to present to the user. Address 'required' items before publishing.
`canPublish`	Yes
`previewUrl`	Yes
`isPublished`	Yes
`publishedUrl`	Yes
`missingFields`	No
`publishPolicy`	No	For edit tools on already-published pages, this is wait_for_separate_user_request to prevent same-turn publishing.
`liveUpdateMessage`	No	Plain-language instruction explaining that an edit to an already-published page is draft-only and must not be published until a later explicit user request.
`liveUpdateRequired`	No	True after an edit to an already-published page when the public live page still needs page.publish to reflect the latest revision.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedMay 27, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds minimal context with the word 'current', implying the URL may change, but no further elaboration on prerequisites or limitations.

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?

The description is a single, clear sentence with no redundant information. It is perfectly concise and front-loaded.

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?

Given the simple read-only nature, annotations covering safety, and an output schema, the one-line description is sufficient to convey the tool's function. The schema documents the editToken requirement for anonymous pages.

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?

Both parameters are fully described in the schema with 100% coverage. The description does not add any additional semantic meaning beyond the schema.

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's purpose: returning the current preview URL for a page. This is a specific verb+resource pairing and distinguishes it from sibling tools like page.publish or page.get.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as page.get or page.publish. No exclusions or context are mentioned.

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

All Create Web Page tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools target distinct resources and actions (blocks, accounts, pages), but page.create and page.create_from_brief both create pages, and page.intake.start vs page.onboarding.start/update are overlapping planning helpers. The detailed descriptions help disambiguate, though an agent might still pause on choosing between them.

Naming Consistency5/5

All tool names follow a consistent lowercase dot-separated resource.action pattern (e.g., block.add, page.publish, account.whoami). Nested resources like page.header.update and page.onboarding.update extend the same rule without mixing conventions.

Tool Count3/5

At 23 tools, the count sits in the borderline 16-25 range. Many tools are specific and justified, but the planning helpers (intake/onboarding) and multiple page creation variants add bulk that could be consolidated.

Completeness3/5

The server covers create, read, update, block management, and publish/unpublish, but misses a page.delete operation, leaving a lifecycle dead-end. Account tools are also minimal, limited to reading/listing without management capabilities.

Resources

Need Help?