Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Create page

create_page

Create a new draft page with a name and slug, optionally defining parent, page type, multilingual SEO fields, and custom fields; add content later in the editor.

Instructions

Create a new draft page with a name and slug (content/blocks are added later in the editor). Optional: parentId, pageType, multilingual displayName/seoTitle/seoDescription, customFields.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "slug": "<slug>"
    },
    "name": "create_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe page's name
slugYesURL-friendly slug, e.g. 'about-us'
pageTypeNoPage type key (defaults to 'page')
parentIdNoParent page id or slug for nested pages
seoTitleNoMultilingual SEO title
descriptionNo
displayNameNoMultilingual display name
customFieldsNoCustom field values for the page type's schema
seoDescriptionNoMultilingual SEO description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / parentId / description
      Previous value: -"Parent page id for nested pages"New value: +"Parent page id or slug for nested pages"
    • addedInput schema / required
      Added value: +[
      +  "name",
      +  "slug"
      +]
  2. First observedv0.73.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact not in annotations: the result is a DRAFT, not a live page, and content must be attached afterward. It says nothing about return value, slug-collision behavior, or permission requirements.

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

Conciseness4/5

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

Two tight clauses with the primary purpose front-loaded and the scope caveat immediately after; nothing is wasted. A short list rather than prose for optional params keeps it scannable.

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 9-parameter creation tool with nested multilingual objects and no output schema, the description covers what is created, the draft state, and the full optional-parameter surface. The only material omission is what the call returns (page id/slug), which an agent needs in order to chain further operations.

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 89%, so the schema already documents name, slug, pageType, parentId, and the multilingual objects. The description enumerates the optional parameters, which aids scanning but adds no semantics beyond what the schema states (e.g., no format hints for parentId vs slug, no guidance on the multilingual key convention). Baseline 3 applies.

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') and scopes it precisely: name and slug only, with the parenthetical clarifying that content/blocks are out of scope. An agent can distinguish this from publish_page, add_block_to_page, and update_page_blocks 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical '(content/blocks are added later in the editor)' implicitly routes the agent to block/page-content tools for anything beyond metadata, which is real usage guidance. However, no sibling is named explicitly and no prerequisites (permissions, slug uniqueness, parent must exist) are stated.

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

Deploy Server

Other Tools