Create Web Page

Update Page Header

page_header_update

Idempotent

Update the link-in-bio page header: displayName, bio, verified checkmark, business-card display style ("photo_hero" large top photo or "avatar"), a short role label (e.g. "Barber · Madrid"), labelPosition, and the header photo (photoUrl; null removes it). Use only the fields you want to change. 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
`bio`	No	Short bio under the display name. Pass null to clear it.
`label`	No	Short role line near the name, e.g. "Brand Designer · Austin, TX". Pass null to clear it.
`pageId`	Yes
`showQr`	No	Reserved: stored but not rendered yet, so no QR appears on the page. Do not promise a page QR; a save_contact block shows a scannable QR of the contact card.
`display`	No	Header style: photo_hero = large business-card top photo, avatar = small round profile photo. Pass null to clear it.
`photoAlt`	No	Alt text for the header photo.
`photoUrl`	No	Header photo URL. Pass null to remove the current photo.
`verified`	No	Show a verified checkmark next to the display name.
`editToken`	No
`displayName`	No	Visible display name in the page header.
`labelPosition`	No
`photoObjectPosition`	No	CSS focal point for the photo_hero crop, e.g. "50% 28%".

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.

Changed2 schema fields changedOct 5, 2026

changedInput schema / properties / showQr / description

Previous value: -"Show a QR code for this page."New value: +"Reserved: stored but not rendered yet, so no QR appears on the page. Do not promise a page QR; a save_contact block shows a scannable QR of the contact card."

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

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnly=false, idempotent=true, destructive=false. The description adds the critical state effect that on published pages the edit produces an unpublished latest revision, plus explicit guardrails against cascading publish/unpublish calls — behavioral context the annotations cannot 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?

Front-loads the field list, which is good, but the publish/unpublish paragraph is repetitive — three sentences restate the same wait-for-user-confirmation rule. Still, every part is actionable rather than filler.

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?

With 12 params, one required, an output schema present, and a mutation that has cross-tool side effects, the description covers the field set, the draft/live distinction, and the required follow-up workflow. Nothing an agent needs to call it safely is missing.

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 75% and the schema already documents null-clearing semantics, maxLengths, and the display enum meanings. The description mostly restates field names (displayName, bio, verified, label, photoUrl) and repeats the photo_hero/avatar distinction, adding little 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?

Names the specific resource (link-in-bio page header) and enumerates the exact fields it edits, so an agent can immediately distinguish it from siblings like page_meta_update and page_theme_update.

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?

Explicitly states to pass only fields being changed, explains the draft-revision consequence for published pages, and gives a hard rule against calling page_publish/page_unpublish in the same turn, including what to tell the user and what user message must precede publishing.

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?