Create Web Page

Get Landing Page

page_get

Read-onlyIdempotent

Read a landing page draft, including its latest content JSON. For anonymous demo pages, include the editToken.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pageId`	Yes
`editToken`	No

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	Improvement hints. Only 'required' items block publishing (they mirror the publish guard); 'recommended' and 'optional' are suggestions to offer after the user has seen the preview, never prerequisites.
`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.

Changed1 schema field changedOct 5, 2026

changedOutput schema / properties / nextSteps / description

Previous value: -"Enrichment hints to present to the user. Address 'required' items before publishing."New value: +"Improvement hints. Only 'required' items block publishing (they mirror the publish guard); 'recommended' and 'optional' are suggestions to offer after the user has seen the preview, never prerequisites."

AddedSep 22, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context by noting the editToken requirement for anonymous demo pages and that the latest content JSON is included, which goes beyond annotations.

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 no wasted words. The key purpose is front-loaded, followed by a relevant conditional detail.

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?

Given that an output schema exists and annotations already convey the safety profile, the description is nearly complete. The main omission is any explanation of pageId, though it is a required UUID and may be self-evident from the name and format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It partially explains editToken ('For anonymous demo pages, include the editToken') but completely omits pageId, the required parameter. This leaves a significant gap in parameter understanding.

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 ('landing page draft') and clarifies that the returned content includes the latest content JSON. It does not explicitly differentiate from siblings like page_preview or account_pages_list, but the scope is clear enough.

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?

Provides conditional guidance for the editToken parameter ('For anonymous demo pages, include the editToken'), but does not say when to use this tool versus alternatives such as page_preview or account_pages_list. Usage is implied rather than explicit.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?