Skip to main content
Glama

Create Site

create_site

Generate a website from business information. Builds the site's home page (roughly 10 sections) and creates the site in draft state with a shareable preview URL; the services and service areas you pass are saved to the site's business info. Additional pages — about, services, contact, and dedicated per-service or per-location pages — are NOT generated by this call today; add them afterwards with add_page. Takes 15-30 seconds. Use list_industries to find valid industry identifiers. Cost: the initial build is free — it spends no AI credits (later AI work such as add_page does) — but every site counts toward the account's site limit (10 sites on the Free plan, 100 on paid plans); at the limit the call fails with a plan-limit message instead of generating.

Annotations: read-only=false, destructive=false, idempotent=false, open-world=false. Why: Creates a brand-new draft site; nothing existing changes (additive, not destructive). Not idempotent: each call creates another site. Closed-world: it talks only to Zarla's own services, including Zarla's AI generation; no third-party entity is addressed. Spends no AI credits.

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": {
      "business_name": "<business_name>",
      "industry": "<industry>",
      "location": "<location>"
    },
    "name": "create_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
phoneNo
addressNo
industryYesIndustry identifier (e.g. "car-detailing", "electrician", "restaurant")
languageNoSite language (default: "en"). Supports 27 languages.
locationYesBusiness location
servicesNoList of services offered
descriptionNoBrief business description — the more detail, the better the content
business_nameYesThe business name
opening_hoursNo
service_areasNoSuburbs/neighborhoods served — the site's whole area list (its map and neighborhoods), up to 12 of up to 60 characters
license_numberNo
years_in_businessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations: reveals the site is created in draft state with a shareable preview URL, discloses runtime (15-30 seconds), clarifies that the build spends no AI credits while later AI work does, and explains that each call consumes a site slot with plan-specific limits (10 Free / 100 paid) and a specific failure mode. What is missing is any note on required account/auth scope or behavior if partial inputs are invalid, so it stops short of a 5.

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 core action and outcome, then layers scope exclusions, timing, and cost in a logical order; almost every clause carries information an agent needs. It is dense and em-dash heavy, but there is little true waste.

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 13-parameter, nested-object creation tool with no output schema, the description covers outcome (draft site with preview URL), side effects (services/service areas saved), latency, cost and quota consequences, and what is deliberately not produced. An agent has enough to call it correctly and know what comes back.

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 only 54% across 13 parameters, but the description compensates on the important ones: it explains that services and service_areas are persisted into the site's business info, and routes the agent to list_industries for the required industry identifier. It adds no meaning for the remaining fields (email, phone, description, opening_hours, license_number, years_in_business, language), which rely solely on schema text.

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 concrete verb and resource — 'Generate a website from business information' — and immediately scopes what is built (home page, ~10 sections) versus what is not (about, services, contact, per-service/per-location pages). An agent can separate it from add_page 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?

Names the alternative explicitly ('add them afterwards with add_page'), gives a prerequisite for a required parameter ('Use list_industries to find valid industry identifiers'), and states the conditions under which the call fails (site limit reached). When-to-use, what-to-do-next, and a failure precondition are all covered.

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.