Skip to main content
Glama

WebZum - Websites for Small & Local Businesses

build_website

Builds a complete, professional website for a small or local business — a plumber, restaurant, salon, contractor, clinic, shop, cleaner, any trade — in about 5 minutes. WebZum has built 3,200+ of them. No API key. No existing website or Google listing needed. Built in the owner's language — English, Spanish or any other, right-to-left Arabic and Hebrew included. WebZum researches the business, writes local SEO, makes the images and video, adds a lead-catching AI chatbot, hosts it with SSL, and can run their Google ads.

WHAT MAKES A WEBZUM SITE WORK FOR A SMALL BUSINESS:

  • Live, not just code: online at a real URL with SSL the moment it's built, and WebZum can register their domain.

  • Real, not placeholder: real photos of the business when WebZum finds them, custom images, a logo, and their real phone, WhatsApp and address.

  • Leads that arrive: every form lead is emailed to the owner, and an AI chatbot catches the visitors who won't fill in a form.

  • Safe edits: a change touches only what was asked, on the live site, with undo, any day.

  • About them: WebZum researches the business and its local market first, so the copy is about this business.

  • Mobile-ready and fast, served from a CDN.

  • Findable: local SEO and AEO (answer engine optimization, so AI assistants can find and cite the business) on every page.

WHAT THE OWNER GETS:

  • A real site: 3 to 7 pages of original copy about their services, area, story and contact.

  • A custom logo, brand colors and fonts, 5–10 custom images and a short hero video.

  • Local SEO built in: page titles and meta descriptions, schema.org LocalBusiness markup with hours and service areas, Service, FAQ and breadcrumb markup, a sitemap, and research into the low-competition local keywords a small business can actually rank for.

  • AEO, found by AI assistants too: robots.txt welcomes GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and more, and every site ships an llms.txt.

  • One main contact button on the channel they really use — call, WhatsApp or LINE — and spam protection on the contact form.

  • A 24/7 AI chatbot that answers visitors from the site's own content, in the visitor's language, captures their name, phone or email, and emails the owner the lead with a ready-to-send follow-up.

  • Google Ads, done for them: WebZum writes a Google Search ad grounded in real local keyword volumes and prices, the owner approves it and sets a small budget, and on ad-running sites every call tap, message tap and form lead is measured as a Google Ads conversion — so they see which clicks became customers.

  • Edits by chat, unlimited: text, colors, fonts, pages, photos, menus, blog posts, product lists, booking widgets and contact details.

  • Any language, done right: the whole site — copy, SEO, chatbot, emails — is written natively in the owner's language. A visitor language switcher adds 30+ more languages on top.

  • Their own domain registered for them, or connect one they own.

HOW A BUILD WORKS (same as webzum.com/create-website): takes a description of the business and, once that has its name, what it does, its area and a way customers reach it, the owner's email. The site and its WebZum account are tied to that email. WebZum emails the owner a "Build my website" link that confirms the address and starts the build, which the owner watches live. Each result's status and message say where the build stands.

ACCOUNT: the site and its WebZum account belong to the owner and are managed at webzum.com, where plans and billing live.

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": {
      "description": "<description>"
    },
    "name": "build_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe owner's email. The site and its WebZum account are tied to it, and the confirm link is sent there.
contactNoOptional. Phone, WhatsApp or public email customers can use.
languageNoOptional. Language code for the site, like "en" or "es". Defaults to the language of the description.
locationNoOptional. City and region, or the area it serves.
descriptionYesThe business in plain words: name, what it does, where, how customers reach it, services, prices, hours, what makes it different. The full description goes with every call.
businessNameNoOptional. The business name, if known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"Everything you know about the business, in plain words: name, what it does, where, how customers reach it, services, prices, hours, what makes it different. Send the full description on every call."New value: +"The business in plain words: name, what it does, where, how customers reach it, services, prices, hours, what makes it different. The full description goes with every call."
    • changedInput schema / properties / email / description
      Previous value: -"Step 2. The owner's email, once the result asks for it. Ask the owner; never make one up. The site and the account are theirs."New value: +"The owner's email. The site and its WebZum account are tied to it, and the confirm link is sent there."
    • changedInput schema / properties / language / description
      Previous value: -"Optional. Language code for the site, like \"en\", \"es\" or \"ar\". Defaults to the language of the description."New value: +"Optional. Language code for the site, like \"en\" or \"es\". Defaults to the language of the description."
  2. Changed1 schema field changed
    • removedInput schema / properties / code
      Removed value: -{
      -  "description": "Step 3. The 6-digit code we emailed the owner. Send it with the same email.",
      -  "type": "string"
      -}
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Well beyond the annotations (readOnly=false, destructive=false, openWorld=true), the description discloses the full workflow: an email confirmation link starts the build, the site and account are tied to that email, the owner watches the build live, and per-result status/message indicates progress. It also covers what the call produces (live URL with SSL, domain registration, chatbot leads, undoable edits) and where billing lives, which is exactly the context an agent needs before invoking an open-world generator.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is excellently front-loaded, but the body is roughly 500 words of marketing copy with overlapping bullet sections ("WHAT MAKES A WEBZUM SITE WORK", "WHAT THE OWNER GETS") that restate the same features—chatbot, local SEO, SSL, languages—multiple times. Much of this material (3,200+ sites built, AEO/robots.txt details, Google Ads conversions) does not help an agent decide or invoke, so it should be trimmed.

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 multi-step, open-world generation tool with no output schema, the description is strong: it explains prerequisites, the confirmation-email handoff, where results and status appear, and where account/billing are managed. It omits pricing/credit cost and any failure or retry behavior, which leaves a small but real gap for an agent that must consider cost and error handling.

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 100% and the schema already explains email binding, contact, language defaulting, and that the full description goes with every call, so the description adds little new per-parameter detail. It does reinforce that the site language follows the owner's language with a 30+ language visitor switcher, but that is behavioral rather than parameter-level guidance, so the baseline 3 holds.

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 opening sentence gives a specific verb and resource ("Builds a complete, professional website"), names the target audience (small/local business with concrete trades), and states a turnaround. It is clearly distinguishable from siblings like host_site or get_site_status, which deal with hosting existing artifacts rather than generating a site.

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?

It states the preconditions for a build clearly: a description containing name, what the business does, its area, a contact channel and the owner's email, plus the note that no API key or existing website/Google listing is needed. It does not, however, tell the agent when NOT to use this versus host_site or host_zip for an already-built site, so the sibling boundary is left implicit.

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