simplepages

Add a website redirect

create_redirect

Add a URL redirect rule to a website, sending one path to another. Use this when a page moves or a URL changes, so existing links keep working. Redirect rules take effect when the site is next published; publishing is a separate step.

Input Schema

TableJSON Schema

Name	Required	Description
`siteId`	Yes	The website these redirects belong to (id from list_sites).
`toPath`	Yes	Where to send it: a path like "/pricing", or a full https:// URL for another site. With a wildcard source, ":splat" in this value is replaced by the matched remainder.
`fromPath`	Yes	The path to redirect FROM, starting with "/", e.g. "/old-pricing". May end in "/" to match everything beneath it, e.g. "/blog/".
`statusCode`	No	301 for a permanent move (the default, and what search engines should follow), 302 for a temporary one.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes	Always states that the rule is not live until the site is published.
`siteId`	Yes
`toPath`	Yes
`fromPath`	Yes	The stored path, after normalisation.
`wildcard`	Yes	True when the source path ends in "/*", so it matches everything beneath it rather than one exact path.
`redirectId`	Yes
`statusCode`	Yes	301 permanent, 302 temporary.

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses the key behavioral trait that redirects only take effect after the next publish, which is a separate step. This adds important context for the agent. 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?

The description is two concise sentences that are front-loaded with the primary action and then provide usage guidance and a key caveat. No unnecessary words.

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 the tool's moderate complexity (4 params, output schema present), the description covers purpose, usage, and the deferred publication effect. Parameter details are handled by the schema, and the output schema covers return format. It lacks only explicit mention of potential conflicts or idempotency, which are not essential.

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 description coverage is 100% with detailed parameter descriptions for all fields, including wildcard and status code semantics. The description adds no additional parameter information, so baseline score of 3 is appropriate.

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?

Clearly states it adds a URL redirect rule to a website, with the specific purpose of handling moved pages or changed URLs. Distinguishes from sibling tools like add_page_to_site or delete_redirect by focusing on redirect creation.

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?

Gives a concrete use case: 'Use this when a page moves or a URL changes, so existing links keep working.' Also notes that redirects take effect on next publish, implying when to expect activation. Does not explicitly list alternatives or exclusions, but the context is clear.

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?