simplepages

Edit a landing page

edit_page

Change an existing landing page by describing what to change in plain language (e.g. "change the headline to X", "add a pricing section", "make the hero button say Book now"). Edits the page's current content in place and saves it to the draft. The change is not published until you publish separately. Works for both standalone pages and pages inside a site. Use get_page / list_pages / list_sites to find the page id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pageId`	Yes	The page UUID (id from list_pages / get_page).
`instructions`	Yes	What to change, in plain language. Be specific about the target (which section, text, or button) and the desired result. The page's existing style, layout, and images are preserved.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes
`pageId`	Yes
`status`	No	Present only when something changed.
`changed`	Yes	False when the edit didn't apply (see `summary` for why).
`changes`	No	One line per edit, in the editor's own words. Present only for pages whose editor reports per-edit detail; absent is not a failure, and `editsApplied` is the count either way.
`editUrl`	Yes
`summary`	Yes	One line on what changed, or why nothing did.
`opsApplied`	Yes	Deprecated alias of `editsApplied`. Prefer that field.
`previewUrl`	Yes
`editsApplied`	Yes	How many edits were written. Always present; 0 if none.
`previewCurrent`	No	Whether previewUrl already reflects this edit. False means the edit is saved but the preview may lag, so open editUrl to see it now. Absent means we cannot say, not that it is stale.

TDQS

A4.7/5.0

Behavior5/5

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

The description goes beyond the readOnlyHint annotation by explaining edits happen in place, results go to a draft, the change is not published until separately published, and existing style/layout/images are preserved. This is meaningful behavioral context not derivable from annotations alone.

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?

Four focused sentences lead from purpose to examples to behavior to prerequisites. Each sentence adds distinct information, and there is no repetition or 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?

Given only two parameters, existing annotations, and an output schema, the description fully covers what tool does, what happens to the draft, publish semantics, page types supported, and how to locate the required pageId. It is sufficiently complete for an agent to invoke correctly.

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?

The schema already covers both parameters thoroughly (100% coverage), so the baseline is 3. The tool description adds value with plain-language instruction examples for the instructions parameter and extends page ID lookup guidance to list_sites, raising it slightly above baseline.

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 states the tool's exact function: changing an existing landing page using plain-language instructions, with concrete examples. It clearly distinguishes from sibling create_page by emphasizing 'existing' and 'change in place'.

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?

The description clearly indicates this is for editing existing pages, explains that changes are saved to draft and not published, and tells users to find the page id via get_page/list_pages/list_sites. However, it does not explicitly name create_page as the alternative for new pages, so it stops short of an explicit when-not-to-use statement.

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

All simplepages 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/5.0

Disambiguation5/5

Each tool has a distinct purpose, with clear differentiation between creating standalone pages vs. adding to sites, and separate analytics for pages, sites, and workspaces.

Naming Consistency4/5

Mostly follows verb_noun pattern, but uses both 'add' and 'create' for similar actions, and 'delete' vs 'remove' inconsistently.

Tool Count4/5

20 tools cover a broad range of functionality (pages, sites, redirects, scripts, webhooks, analytics, leads), which is reasonable but slightly on the higher side.

Completeness3/5

Covers CRUD for most entities, but lacks delete operations for pages, sites, scripts, and webhooks (except redirects), leaving notable gaps.

Resources

Need Help?