Skip to main content
Glama

Create a draft site

create_site

Creates a draft website from the business details, a starter layout and, for the best result, the pages and section text you have written for this business. Without pages, the layout's plain default wording is used. Nothing is public until publish_site. The free web address is .mywebdesk.app.

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": {
      "brief": "<brief>",
      "layout": "<layout>"
    },
    "name": "create_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the site: en (default) or fr.
slugNoWanted web address before .mywebdesk.app. Suggested from the business name when left out.
briefYes
pagesNoYour first draft of the pages. When left out, the layout's default pages and text are used.
themeNo
layoutYesStarter layout. See list_templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds the more important behavioral facts: the output is a non-public draft, unpublishable until publish_site, and missing pages fall back to default copy. It omits what happens on slug collision or repeat calls, which matters given idempotentHint=false and the risk of creating duplicate sites.

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 short sentences, front-loaded with the verb and resource, then the pages-vs-default rule, then the publication boundary, then the address format. Nothing is repeated from the schema and no sentence is filler.

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 deeply nested creation tool it covers the genuinely ambiguous decisions (whether to pass pages, what the slug produces, that the site stays private). With no output schema, the one real gap is that it never indicates what is returned, such as a site identifier needed for the follow-up publish_site call.

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 coverage is 67%, so the description's contribution is helpful but partial: it explains why pages is optional, that layout is only a starter, and that slug becomes the free <slug>.mywebdesk.app address. It says nothing about theme (tone/palette) or lang, leaving those to the schema.

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 ("Creates a draft website") plus the inputs it draws from (business details, starter layout, optional pages/section text). It also draws the boundary with the sibling publish_site by stating nothing is public until then, so an agent can distinguish creation from publication 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 Guidelines4/5

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

Gives clear when-to-use context: supply pages and section text "for the best result", otherwise the layout's default wording is used, which tells the agent both the preferred and fallback paths. It does not explicitly exclude or warn against alternatives such as update_site for an existing site, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources