Skip to main content
Glama
julioMeif

Template Vault MCP

generate_site

Destructive

Generate a business website after collecting a complete business profile through discovery. Returns a job ID immediately; poll for the live site URL after 30-90 seconds.

Instructions

Generate a new website for a business. Returns a jobId immediately — the build runs asynchronously (~30-90s). Poll get_generation_status to find the site_id + preview URL once it's done.

PREREQUISITE: You MUST have called discover_business_needs first and asked the user the resulting questions. Calling generate_site without a populated businessProfile produces a poor site missing integrations — WhatsApp buttons, Instagram embeds, booking widgets — and that embarrasses both the user and Template Vault.

A populated businessProfile should include AT LEAST: a phone or whatsapp number, hasPhysicalLocation (+ address if true), hasSocialMedia (+ handles if true), and languages. If the user truly refuses discovery, pass { skippedDiscovery: true } so the backend can warn in the admin log.

Content policy: Template Vault declines categories listed at https://www.the-template-vault.com/docs/mcp/content-policy (adult content, hate speech, scams, illegal goods, CSAM, impersonation/phishing). Obvious matches are rejected synchronously with a clear error; subtler cases are caught by the underlying Anthropic model.

Counts against the user's monthly generation quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
businessNameYesCustomer-facing business name. Will be shown in the navbar.
businessDescriptionYes2-3 sentences from the discovery conversation — what they do, who for, vibe. Pull directly from the user's own words; do not invent.
industryYesIndustry category — e.g. 'wellness', 'restaurant', 'photography', 'pool builder', 'fitness'. Used for SEO + integration detection + personality picking. Be specific (prefer 'pool builder' over 'construction').
personalityNoOptional visual personality id (call list_personalities first to see options). If omitted, the AI picks one based on industry + description. NEVER pick `minimal` for a service contractor (pool/electric/plumb/handyman) or restaurant — those need `classic`. NEVER pick `glass` for a service contractor — too cold.
pageCountNoNumber of pages to generate (1-4). One-page sites convert best for small businesses.
localesNoLocale codes — e.g. ['en'] or ['en','es'] or ['en','fr']. Max 3. For South Florida businesses always include 'es' alongside 'en' — most customers are bilingual. Each adds ~5s of latency.
businessProfileYesREQUIRED for a good result. Drives all integrations + smart-block selection. An empty profile gives a sparse, text-only site.
Behavior5/5

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

Discloses async execution (~30-90s), quota consumption, and content policy rejections. Annotations indicate destructiveHint=true and readOnlyHint=false; description aligns with and adds detail about the destructive creation process. No contradiction.

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?

The description is long but well-structured with sections (prerequisite, content policy). Information is front-loaded, but some redundancy exists (e.g., mentioning async twice). Still efficient for the complexity.

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?

Given the complexity (7 parameters, nested object, async, prerequisites, content policy, quota), the description covers all necessary aspects: return value, polling, prerequisites, edge cases, and restrictions. No output schema, but the polling mechanism is explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions. The tool description adds extra context: businessProfile is emphasized as required for good results, skippedDiscovery only when user refuses, and specific advice for businessDescription and personality. This significantly enhances understanding.

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?

The description clearly states the tool's purpose: generating a new website. It specifies the async nature and return of a jobId. It distinguishes itself from sibling tools like discover_business_needs and get_generation_status by explaining prerequisites and subsequent polling.

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?

Explicit prerequisites are given: must call discover_business_needs first. Provides guidance on when to use skippedDiscovery if user refuses. Mentions content policy restrictions. Clearly sets context for tool usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/julioMeif/template-vault-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server