Skip to main content
Glama

WebZum - Websites for Small & Local Businesses

by io.github.suprraz
OverviewDiscussionsAdmin

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 2,900+ 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.

Input Schema

TableJSON 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

A3.5/5.0
Behavior4/5

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

Annotations are shallow (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds substantial behavioral context beyond them: the ~5-minute build, the email 'Build my website' confirmation that starts the build, ownership/account binding to the email, and 'each result's status and message say where the build stands.' That is genuinely useful for invocation, though much of the rest is output-artifact marketing rather than tool behavior.

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 purpose is front-loaded in sentence one, but the body is a long marketing brochure — multiple bulleted sections ('WHAT MAKES A WEBZUM SITE WORK', 'WHAT THE OWNER GETS') with feature sales copy (AEO, chatbots, Google Ads, llms.txt) that adds little to an agent's decision or invocation. This is over-specification that buries the operational content.

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 complex, open-world build tool with no output schema, the description does supply what an agent needs to call it correctly: required email, the description field's expected content, and the resulting confirmation/status flow. It is complete on essentials, though the volume of promotional material dilutes signal.

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 description coverage is 100%, so the schema already documents all six parameters. The description loosely restates what the description field should contain (name, what it does, area, how customers reach it) and confirms the email drives account/site binding, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb+resource and scope: 'Builds a complete, professional website for a small or local business.' It is immediately clear what the tool produces. It does not explicitly differentiate from siblings like host_site or host_zip, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The 'HOW A BUILD WORKS' paragraph implies usage by describing prerequisites (a description containing name, what it does, area, contact, plus the owner's email). But there is no explicit when-to-use vs the sibling hosting/status tools and no stated exclusions or alternative routes.

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

All WebZum - Websites for Small & Local Businesses toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources