Skip to main content
Glama

Create a new site

create_site

Creates a new website at https://.hostilo.page and publishes it in the same call. Content is optional: html for a single-file page, files for a multi-file site (index.html plus css/, js/, images, fonts; same format as publish_files: other files go to assets/ and links in index.html are fixed), or template to start from a ready-made Hostilo design (see list_templates) with your name, phone and colour filled in. Counts toward the plan's site limit.

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

Input Schema

NameRequiredDescriptionDefault
htmlNoOptional full HTML of a single-file page (max 5 MB). Use this or files.
langNoLanguage of the template content (default en).
nameYesSubdomain: 3-30 lowercase letters, digits or hyphens.
filesNoOptional list of files for a multi-file site. Include index.html; it becomes the page.
templateNoOptional: start from a Hostilo template (slug from list_templates, e.g. "cafe-menu", "local-service"). Use instead of html/files.
template_fieldsNoTemplate fields from list_templates, e.g. {"name":"Linden Café","phone":"+48 600 100 200","accent":"#c2603a"}. Missing fields get sample content.
template_photosNoDefault true: frames for the site owner photos (sizes shown, swapped later in the editor). false: the version without photos, with icons and illustrations, ready to publish. Only templates with photos_optional in list_templates have the version without photos.
template_variantNoTemplate variant from list_templates, e.g. the industry of "local-service": plumber, electrician, hair-salon, accountant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / template_photos / description
      Previous value: -"Default true: frames for the site owner photos (sizes shown, swapped later in the editor). false: the version without photos, with icons and illustrations, ready to publish. Only templates with photo_slots in list_templates differ."New value: +"Default true: frames for the site owner photos (sizes shown, swapped later in the editor). false: the version without photos, with icons and illustrations, ready to publish. Only templates with photos_optional in list_templates have the version without photos."
  2. Changed1 schema field changed
    • addedInput schema / properties / template_photos
      Added value: +{
      +  "description": "Default true: frames for the site owner photos (sizes shown, swapped later in the editor). false: the version without photos, with icons and illustrations, ready to publish. Only templates with photo_slots in list_templates differ.",
      +  "type": "boolean"
      +}
  3. Changed6 schema fields changed
    • addedInput schema / properties / files
      Added value: +{
      +  "description": "Optional list of files for a multi-file site. Include index.html; it becomes the page.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "content": {
      +        "description": "File content: plain text, or base64 when encoding is \"base64\".",
      +        "type": "string"
      +      },
      +      "encoding": {
      +        "default": "utf-8",
      +        "description": "Use \"base64\" for images, fonts and other binary files.",
      +        "enum": [
      +          "utf-8",
      +          "base64"
      +        ],
      +        "type": "string"
      +      },
      +      "path": {
      +        "description": "Path relative to the site root, e.g. \"index.html\", \"css/style.css\", \"img/logo.png\".",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "path",
      +      "content"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 300,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / properties / html / description
      Previous value: -"Optional full HTML of the page (max 5 MB)."New value: +"Optional full HTML of a single-file page (max 5 MB). Use this or files."
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "Language of the template content (default en).",
      +  "enum": [
      +    "en",
      +    "pl",
      +    "de",
      +    "es",
      +    "fr",
      +    "pt",
      +    "zh"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / template
      Added value: +{
      +  "description": "Optional: start from a Hostilo template (slug from list_templates, e.g. \"cafe-menu\", \"local-service\"). Use instead of html/files.",
      +  "type": "string"
      +}
    • addedInput schema / properties / template_fields
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "description": "Template fields from list_templates, e.g. {\"name\":\"Linden Café\",\"phone\":\"+48 600 100 200\",\"accent\":\"#c2603a\"}. Missing fields get sample content.",
      +  "type": "object"
      +}
    • addedInput schema / properties / template_variant
      Added value: +{
      +  "description": "Template variant from list_templates, e.g. the industry of \"local-service\": plumber, electrician, hair-salon, accountant.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, non-idempotent, open-world write, so the safety bar is met. The description adds genuinely useful behavior the annotations cannot: the site is published immediately, a URL is derived from the name, and the call consumes the plan's site limit.

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?

Front-loaded with the action and URL, then the three content modes in a single dense paragraph. It is information-rich with little waste, though the long parenthetical about assets and link fixing is harder to parse than a short bulleted breakdown would be.

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 an 8-parameter write tool with no output schema, the description covers the important behavior: immediate publish, URL shape, content-mode exclusivity, and the plan limit. It stops short of saying what is returned (site URL/object) or what happens on name collisions or a failed publish mid-call.

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 adds meaning by explaining that files follow the publish_files format, non-index files are routed to assets/, and links in index.html get rewritten, plus that template_fields fills name/phone/colour and missing fields get sample content.

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 new website") plus the resulting URL pattern and the fact that publishing happens in the same call. It also names sibling tools (publish_files, list_templates), so an agent can distinguish it from list_templates or import_zip without opening a 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?

Clearly frames the three mutually exclusive content modes (html for single-file, files for multi-file, template from list_templates) and points to list_templates for template discovery. It lacks explicit 'when not to use' guidance, e.g. using update_site for an existing site or import_zip instead of files.

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.