Skip to main content
Glama

Wordy Page

by page.wordy
OverviewDiscussionsAdmin

Create or Update a Multi-Page Website

create_or_update_page
Destructive

Create a new single-page or multi-page website or update an existing site on wordy.page. Supports up to 10 pages per site, simple Light or Dark mode (theme: "light" or "dark"), one Unsplash header image per page (photo on the home page and on each section, which also renders a 50%-opacity blurred full-viewport background), plain-text formatting limited to ALL CAPS blue light-bold highlights (do NOT use bold Markdown asterisks) and space/tab indentation (blank lines stay blank, no dividers), safe plain-text HTML/code escaping, automatic URL/email linking, and an optional contact form on any page (cf: true on the home page or a section; Email + Message only). If authenticated with a matching session_token, publishes immediately (status: "live"); otherwise emails a one-tap verification/publish link to owner_email (status: "Verify email").

Input Schema

NameRequiredDescriptionDefault
slugYesTarget web address slug (3-40 chars, lowercase letters/digits/hyphens), published at https://wordy.page/<slug>/.
photoNoOptional single header image for the home page: an Unsplash photo id from `search_photos`. Renders below the page name and above the text, with photographer credit. One image per page.
themeNoVisual theme ("light" or "dark").light
titleYesSite name displayed in the sticky top header bar (max 36 characters; stacks up to 2 lines on mobile without changing header height, and clicks back to the first home page).
headingYesHome page heading (H1, max 80 characters).
sectionsNoOptional additional sub-pages (up to 9 extra pages, home + 9 = 10 pages total, each given its own URL `/<slug>/<page-slug>/` and navigation menu item).
from_slugNoOptional old slug if renaming/moving an existing site you own to a new slug.
descriptionYesHome page body text (max 20,000 chars). Formatting is plain text with ONLY two features: indentation (leading spaces/tabs are preserved) and ALL CAPS (contiguous sequences of 2+ uppercase letters render blue and lightly bold; do NOT use **bold** asterisks). Each \n is a line break and blank lines (\n\n) simply stay blank lines (no <hr> dividers). Plain URLs, emails and [anchor](https://...) links are auto-linked; HTML is escaped. Images are NOT placed in text: give each page one header image with its `photo` field.
login_tokenNoOptional 32-character one-time token from an emailed `https://wordy.page/pages?login=<token>` link to redeem and authenticate right away.
owner_emailYesOwner email address (receives the one-tap verification link and any contact form messages; never displayed publicly).
session_tokenNoOptional 30-day session token (`st`) if already authenticated for `owner_email`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false. The description adds useful behavior beyond that: page limits, formatting/escaping/linking rules, contact-form delivery, and the immediate-publish versus email-verification flow; it still does not clarify whether updating overwrites existing pages/content, which matters for a destructive mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and key constraints are front-loaded, but the body is a single dense paragraph with many parenthetical formatting rules. Much of that detail duplicates the rich schema, so trimming or splitting would improve scanability.

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?

For an 11-parameter mutation tool with rich schema and annotations but no output schema, the description covers purpose, limits, formatting, contact forms, authentication, and publish status well. It still lacks explicit return/error behavior and precise update-overwrite semantics.

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 100%, so the schema already documents slug, theme, photo, sections, owner_email, session_token, and other fields. The description repeats several field constraints such as theme, photo, cf, and formatting, but adds little parameter-level meaning beyond the schema and omits explicit discussion of from_slug and login_token.

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 and resource: creating a new single-page or multi-page website or updating an existing site. It also states the 10-page scope and clearly distinguishes this mutation tool from sibling read/search tools such as get_page, list_pages, check_slug, and search_photos.

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?

It clearly states the creation-versus-update use case and explains the authentication-dependent publish path. However, it does not direct the agent to check_slug first or explain when to use get_page, list_pages, or search_photos instead.

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

All Wordy Page toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources