Skip to main content
Glama

Generate landing page

generate_landing_page
Read-onlyIdempotent

Generate a complete, responsive single-file HTML landing page for a small business: hero, services, WhatsApp/email call to action, contact section and footer, with inline CSS and SEO meta tags. Requires business_name; optional tagline, description, services, city, whatsapp, email, language (es|en), color and cta_text. Returns the HTML document as text. Free, deterministic template, nothing is stored.

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>"
    },
    "name": "generate_landing_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity or area served
colorNoBrand color as hex, e.g. #0f766e
emailNoContact email
taglineNoShort headline, e.g. 'Plumbing repairs in 24 hours'
cta_textNoMain button text
languageNoPage languagees
servicesNoUp to 8 services. Use 'Title: short description' to add a description. GET: comma-separated
whatsappNoWhatsApp number in international format, digits only, e.g. 5491122334455
descriptionNoOne or two sentences about the business
business_nameYesBusiness or project name (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts beyond that: output is returned as text, the template is deterministic, it is free, and nothing is stored.

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?

Two sentences, front-loaded with what is produced and what it costs. The second sentence's enumeration of parameters is somewhat redundant against a fully documented schema, but it is compact and readable.

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 parameter-rich generator with no output schema, the description does the necessary work: it describes the document's structure, states the return type, and disclaims storage. It leaves minor gaps such as output size or responsiveness caveats, but nothing an agent needs to invoke it correctly is missing.

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 ten parameters with constraints (maxLength, enum, pattern, defaults). The description's parameter list largely repeats that information rather than adding syntax or interaction detail, so baseline 3 applies.

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 specific verb+resource ('Generate a ... single-file HTML landing page') and enumerates the exact sections produced (hero, services, CTA, contact, footer) plus inline CSS and SEO meta tags. An agent can distinguish this from the unrelated sibling get_service_info at a glance.

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 clearly signals the context of use (small business landing page) and states the one hard prerequisite ('Requires business_name'), with everything else marked optional. It does not name when-not-to-use or an alternative, but no plausible competing tool exists in the sibling set.

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