Skip to main content
Glama

b12_website_generator

Create a ready-to-publish website for your business by providing its name and a brief description. The tool generates a link to claim and publish your website for free.

Instructions

Generates website for business by a given business name and short description
and prints output in the chat using the following format:
Your new website for *{{The business name}}* is ready! [Sign up to see the website]({{The link to claim newly designed website.}}) and publish it for free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYesThe short description of the business in less than 1000 characters.
nameYesThe name of the business.

Implementation Reference

  • The main handler for CallToolRequestSchema that executes the 'generate_website' tool logic by generating a B12 signup URL based on provided business name and description.
    server.setRequestHandler(CallToolRequestSchema, request => {
      try {
        const { name: toolName, arguments: args } = request.params
    
        if (!args) {
          throw new Error('Business name and description are not provided')
        }
    
        if (toolName === 'generate_website') {
          const { name, description } = args
          return {
            content: [{
              type: 'text',
              text: `https://b12.io/signup/?utm_medium=chat&utm_source=mcp-server&intent=ai-websites&utm_content=website-generator&business_name=${encodeURIComponent(String(name))}&business_description=${encodeURIComponent(String(description))}`
            }],
            isError: false,
          }
        }
        return {
          content: [{ type: 'text', text: `Unknown tool: ${toolName}` }],
          isError: true,
        }
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        }
      }
    })
  • Schema definition for the 'generate_website' tool, including input schema, description, and annotations.
    const WEBSITE_GENERATION_TOOL = {
      name: 'generate_website',
      // Make sure the description is in sync with tool description in manifest.json
      description: 'Generates a website from a business/project name and short description, then presents a link (in markdown format) to sign up and see the website.',
      annotations: {
        readOnlyHint: false,
        destructiveHint: false,
        idempotentHint: false,
        openWorldHint: true,
        title: 'Generate Website',
      },
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'The name of the business.'
          },
          description: {
            type: 'string',
            description: 'The short description of the business in less than 1000 characters.'
          },
        },
        required: ['name', 'description']
      }
    }
  • src/server.js:49-51 (registration)
    Registration of the tool via ListToolsRequestSchema handler, exposing the WEBSITE_GENERATION_TOOL.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [WEBSITE_GENERATION_TOOL],
    }))
  • src/server.js:10-20 (registration)
    Creation of the MCP server instance named 'b12-website-generator', which provides the website generation tool.
    const server = new Server(
      {
        name: 'b12-website-generator',
        version: '0.1.0',
      },
      {
        capabilities: {
          tools: {},
        },
      },
    )
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the output format (prints in chat with specific text) but lacks critical details like whether this is a read-only or mutation operation, authentication needs, rate limits, or error handling. The description implies a generative action but doesn't clarify if it's a simulation or actual website creation.

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 concise and front-loaded, stating the core function in the first sentence and detailing the output format in the second. Both sentences earn their place by providing essential information without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (generative action with 2 parameters) and no annotations or output schema, the description is minimally adequate. It covers the basic purpose and output format but lacks completeness in behavioral context, usage guidelines, and detailed parameter insights, leaving gaps for an AI agent.

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 fully documents both parameters (name and description). The description adds no additional semantic meaning beyond what the schema provides, such as examples or constraints, resulting in the baseline score of 3.

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 description clearly states the tool's purpose: 'Generates website for business' with specific inputs (business name and description) and output format. It distinguishes the action (generate) and resource (website), but since there are no sibling tools, it cannot differentiate from alternatives, keeping it 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 Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or limitations. It simply states what the tool does without context for usage decisions, resulting in minimal guidance.

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

Related 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/b12io/website-generator-mcp-server'

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