Create Web Page

Update Landing Page Block

block.update

Idempotent

Patch one content block by stable blockId. Provide a props patch (merged into existing props) and/or a new type. Block types and props are validated against the strict per-type schema. For already-published pages, this saves an unpublished latest revision only. Do not call page.publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page.publish. Do NOT call page.unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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.

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already indicate non-read-only and non-destructive, but the description adds substantial context: props are merged into existing props, block types are validated against a strict per-type schema, and for published pages only an unpublished latest revision is saved. The publish/unpublish workflow warnings go far beyond what annotations convey.

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?

The description is long, but every sentence carries important operational guidance: patch semantics, merge behavior, validation, revision behavior, and explicit workflow cautions. It is dense and information-preserving, though slightly verbose in the publish/unpublish section.

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 rich oneOf schema and output schema, the description covers the key runtime behaviors an agent needs: how props merge, how revision creation works on published pages, and the critical do-not-publish-in-same-turn rule. There are no obvious gaps that would cause an agent to misuse the tool.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds meaningful semantics by explaining that 'props patch' is merged into existing props, and that block types are validated against the strict per-type schema. This clarifies the partial-patch intent beyond the raw schema fields.

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 opens with a specific verb+resource+mechanism: 'Patch one content block by stable blockId.' It clearly distinguishes block.update from siblings like block.add, block.delete, and block.reorder by focusing on patching an existing block.

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

Usage Guidelines5/5

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

The description explicitly says when to use this tool (patch an existing block) and provides strong exclusions: do not call page.publish in the same turn, wait for a separate explicit user request to publish, and do not call page.unpublish. It also clarifies the revision behavior for published pages, making it unmistakable when this tool is appropriate.

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?