Skip to main content
Glama
swebsy

swebsy-mcp

Official
by swebsy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

swebsy_create_page

Create a new blank page in the project, optionally select it, and return its id and fileName. Use it to add extra pages, then fill and link them.

Instructions

Create a NEW blank page in the project and (by default) select it. Returns the new page's id and fileName. The page starts nearly empty — fill it with replace_page_content or add_section, and point a navbar/link at it with link_page. Use THIS to add an additional page; use replace_page_content (NOT this) to overwrite the current page's content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name / title for the page (e.g. 'About').
selectNoSelect the new page after creating it. Default true.
fileNameNoOptional URL slug without .html (e.g. 'about'). Use `/` to put the page in a folder: 'blog/first-post' is served at /blog/first-post, 'docs/index' at /docs/. Defaults to a flat slug derived from `name`; auto-deduplicated against existing pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.0
    • changedInput schema / properties / fileName / description
      Previous value: -"Optional URL slug without .html (e.g. 'about'). Defaults to a slug derived from `name`; auto-deduplicated against existing pages."New value: +"Optional URL slug without .html (e.g. 'about'). Use `/` to put the page in a folder: 'blog/first-post' is served at /blog/first-post, 'docs/index' at /docs/. Defaults to a flat slug derived from `name`; auto-deduplicated against existing pages."
  2. First observedv0.8.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the blank initial state, the default auto-select behavior, and the return values. It doesn't cover permissions/auth needs or failure modes, so it stops short of complete behavioral disclosure for a mutation tool.

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 critical creation/blank-state facts are front-loaded, followed by follow-up tooling and the exclusion against the lookalike sibling. Every sentence earns its place with no 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?

For a 3-param creation tool with no output schema, the description states the return values (id, fileName) and the post-creation workflow, which is everything needed to call it and use the result correctly.

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%, so the schema already documents name, select, and fileName in detail (including slug/folder semantics). The description only restates the default-select and slug behavior, adding little beyond the schema. Baseline 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?

States a specific verb and resource (create a NEW blank page) plus what it returns (id, fileName). It explicitly contrasts with the sibling replace_page_content, so an agent can distinguish create-new from overwrite without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly says 'Use THIS to add an additional page; use replace_page_content (NOT this) to overwrite the current page's content,' naming the alternative and the condition that selects it. It also routes follow-up work to add_section and link_page.

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