webbersites-x402-data-api

post_website_page

Webbie page generator: site name, headline, tagline, hero images, content sections, nav, colors — returns a finished responsive standalone HTML page. Three templates (horizon, split, editorial); the seed deterministically picks template + fonts + accent, so reusing it across calls builds a consistent multi-page site. Nav loads from an editable nav.json at view-time. No AI — deterministic templating. ($0.02 per call, paid via x402)

Input Schema

TableJSON Schema

Name	Required	Description
`cta`	No	{text, href}
`nav`	No	[{label, href}] — echoed as nav_json
`logo`	No	Auto-generate mark: {query, colors, shape}
`seed`	No	Reuse the same seed on every call for one consistent site style
`title`	No	Browser/SEO title
`colors`	No	1-2 accents, hex or CSS names
`footer`	No	Footer text
`caption`	No	Kicker above the headline
`content`	No	Sections: [{heading, body}]
`tagline`	No	Supporting line + meta description
`headline`	No	Hero headline
`logo_url`	No	Nav logo image URL
`template`	No	horizon, split, or editorial; omit to let the seed choose
`page_name`	No	'home' = index.html (default), or e.g. 'about'
`site_name`	Yes	Brand/site name (required)
`hero_images`	No	First = hero, extras = gallery

Output Schema

TableJSON Schema

Name	Required	Description	Default
`html`	No
`seed`	No
`style`	No
`filename`	No
`nav_json`	No
`template`	No
`html_bytes`	No

Schema Changelog

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

First observedJul 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations indicate non-read-only, non-destructive, non-idempotent. Description adds pricing, No-AI determinism, and nav loading behavior. No contradiction with 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?

Three concise sentences front-loaded with purpose, no wasted words. Efficiently covers key aspects.

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 high parameter count and output schema, description covers main components, behavior, templates, seed, nav, and pricing. Lacks details on error handling or fallbacks but sufficient for a generator 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 100% so baseline 3. Description adds value by explaining template options (horizon, split, editorial), seed deterministic selection, and nav runtime loading, which enhances understanding beyond schema descriptions.

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 generates a responsive standalone HTML page from specified components (site name, headline, tagline, etc.). It distinguishes from siblings like post_website_build by focusing on single-page generation.

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?

Provides context on deterministic templating, templates, seed reuse for multi-page consistency, and nav behavior. Does not explicitly exclude other tools but implies single-page use case, contrasting with broader site building.

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

All webbersites-x402-data-api 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

A3.9/5.0

Disambiguation4/5

Most tools have distinct purposes, but the SEO-related tools (head_check, full_audit, site_audit, etc.) overlap in scope, potentially causing confusion despite clear descriptions.

Naming Consistency5/5

Tool names consistently follow a get_/post_/delete_ verb pattern with descriptive noun phrases (e.g., get_seo_head_check, post_store_collection), with no mixing of naming conventions.

Tool Count2/5

With 46 tools covering a wide breadth of domains (SEO, accessibility, music, crypto, linting, etc.), the count is excessive for a single server, feeling unfocused and heavy.

Completeness4/5

The tool set covers most core operations for each sub-domain, but minor gaps exist (e.g., missing update for datastore, limited music operations).

post_website_page

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources