Skip to main content
Glama

WebZum - The Hosting Layer for AI-Generated Web Content

by io.github.suprraz

create_lead_gen_site

Destructive

Create a third-party LEAD-GENERATION page about a business (NOT a site for that business itself).

Use this when the goal is to drive qualified search traffic to someone else's business — affiliate pages, review/guide pages, niche directories. The page is branded as an outside guide (e.g. "Best Roofers in San Diego"), refers to the business in the third person, and routes CTAs to the business's existing website.

Differences from create_site:

  • Slug + page brand are SEO-vanity (e.g. "best-roofers-sandiego"), not the candidate's brand name.

  • Voice is third-party guide/reviewer — never first person.

  • Primary CTA is "visit their website"; phone/email demoted.

  • No specific pricing quoted; differentiators emphasized.

  • Locality is judged by category, not just address (IT/SaaS/agency stays category-wide even when a city is on file).

Pass a business candidate object from search_businesses — that business is the one being PROMOTED.

Requires authentication via API key (Bearer token). Generate an API key at webzum.com/dashboard/account-settings.

The page generation happens in the background. Use get_site_status to check progress.

Returns the businessId (a vanity slug) which can be used to access the page at /build/{businessId}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
candidateYesA BusinessCandidate object from search_businesses results (use the _raw array). This is the business the page will promote.
extraInfoNoOptional additional metadata to include with the registration

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations, it discloses authentication via API key, background page generation, and the returned businessId, while framing the content's third-party voice. It does not contradict readOnlyHint/destructiveHint.

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

Conciseness5/5

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

Although fairly long, every sentence carries operational value: purpose, differences, input source, auth, background progress, and return value are all present and front-loaded.

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 tool with no output schema, the description covers input, auth, processing, and return, and points to get_site_status for progress, making it self-sufficient.

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?

The schema already names both parameters, but the description explains that candidate should come from search_businesses' _raw array and is the promoted business, adding semantic guidance beyond field descriptors.

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 opens with a specific action ('Create a third-party LEAD-GENERATION page about a business') and explicitly distinguishes it from create_site by listing differences, making it clear this is not the main business site.

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?

It states exactly when to use it ('drive qualified search traffic to someone else's business') and gives concrete examples; it also contrasts with create_site and tells the agent to pass a search_businesses candidate, plus references get_site_status for monitoring.

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

All WebZum - The Hosting Layer for AI-Generated Web Content toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools have clear, distinct purposes: cloning, creating, hosting, editing, and regenerating different site parts. The main ambiguity is between create_lead_gen_site and generate_geo_page, which both create lead-gen pages but differ in targeting and workflow; however, their descriptions clarify the use cases sufficiently.

Naming Consistency4/5

Tool names follow a consistent lowercase verb_noun pattern (e.g., clone_site, host_file, update_site_html). Minor inconsistencies exist: create vs. generate for similar actions (create_site vs. generate_geo_page) and get vs. list for retrieval (get_hosted_files vs. list_user_sites), but these are predictable and readable.

Tool Count3/5

With 17 tools, the count is slightly heavy for a hosting service, but the variety of operations (creation, cloning, file hosting, editing, regeneration, status, search) justifies most of them. A few tools (e.g., four regenerate_* tools) could potentially be consolidated, but the scope still feels reasonable.

Completeness4/5

The toolset covers the full lifecycle: create, clone, host, list, edit, update, and regenerate site components. Notable gaps include no delete operation for sites or files and no explicit version rollback, but agents can work around these by using host_file to overwrite and relying on site status for progress.

Resources