Pixelesq

Create page

create_page

Destructive

Create a new draft page in a project. The page is empty and not on the live site until it has sections and is published. If the address is already taken a suffix is added, so read the slug in the result. Pass an idempotencyKey to make a retry safe: the same key, project and address name one page, so a call whose answer was lost can be repeated without making a second page. Without a key, look for the address with list_pages before trying again.

Input Schema

Name	Required	Description	Default
`name`	Yes	Page name
`slug`	Yes	The page's address as a path that starts with a slash, e.g. /pricing. A missing leading slash is added.
`language`	No	Language code	en
`projectId`	Yes	The project ID
`idempotencyKey`	No	Stable key for a safe retry: the same key replays the first result instead of applying twice. Reuse a key only for a call that got no answer; after any error, read the page again and use a new key.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / idempotencyKey

Added value: +{
+  "description": "Stable key for a safe retry: the same key replays the first result instead of applying twice. Reuse a key only for a call that got no answer; after any error, read the page again and use a new key.",
+  "maxLength": 128,
+  "type": "string"
+}

First observedOct 17, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=true; the description adds the real behavioral payload: the page starts empty and unpublished, slug collisions silently get a suffix (so results must be re-read), and idempotency is scoped to the key+project+address tuple. These are side effects an agent could not infer from 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?

Four tight sentences, each carrying distinct information: lifecycle state, collision behavior, retry safety, and the no-key fallback. Creation scope is front-loaded and nothing is repeated from the schema.

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 a mutation tool with no output schema, the description covers lifecycle, slug rewriting, and retry semantics thoroughly. It references 'the slug in the result' without saying what else the result contains, a minor gap given no output schema exists to fill it.

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 is 100%, so the baseline is 3. The description still earns credit by adding composite-key semantics for idempotencyKey ('the same key, project and address name one page') that the schema's per-field description does not spell out, plus slug-suffix behavior that changes how the returned slug must be handled.

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?

States a specific verb and resource ('Create a new draft page in a project') plus a lifecycle qualifier (draft, not live) that separates it from create_entry/create_collection and from publish_page. An agent can identify the tool without opening the schema.

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 concrete conditional guidance: pass idempotencyKey for safe retries, and without one, verify the address with list_pages before retrying. It does not discuss sibling alternatives for page creation itself, but for a sole-purpose create tool the retry routing is the relevant decision.

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

All Pixelesq tools Inspect

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

Need Help?