Skip to main content
Glama

maasy_create_landing

Generate a landing page from HTML. Submit brand UUID, page name, and HTML content. Receive landing ID and editor URL to open in the builder.

Instructions

Create a landing page in maasy from HTML. Returns a landing_id and editor_url to open in the builder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoBrand UUID
nameYesLanding page name, e.g. 'Captación Q2 2026'
htmlYesFull HTML content of the landing page
slugNoURL slug (auto-generated from name if omitted)
typeNolanding

Implementation Reference

  • src/index.ts:302-313 (registration)
    Tool registration for 'maasy_create_landing' on the MCP server with schema and handler binding.
    server.tool(
      "maasy_create_landing",
      "Create a landing page in maasy from HTML. Returns a landing_id and editor_url to open in the builder.",
      {
        project_id: z.string().optional().describe("Brand UUID"),
        name: z.string().describe("Landing page name, e.g. 'Captación Q2 2026'"),
        html: z.string().describe("Full HTML content of the landing page"),
        slug: z.string().optional().describe("URL slug (auto-generated from name if omitted)"),
        type: z.enum(["landing", "squeeze", "sales", "webinar", "event"]).optional().default("landing"),
      },
      toolHandler("create_landing")
    );
  • Input schema for the tool: project_id (optional), name (required), html (required), slug (optional), type (optional, defaults to 'landing').
    {
      project_id: z.string().optional().describe("Brand UUID"),
      name: z.string().describe("Landing page name, e.g. 'Captación Q2 2026'"),
      html: z.string().describe("Full HTML content of the landing page"),
      slug: z.string().optional().describe("URL slug (auto-generated from name if omitted)"),
      type: z.enum(["landing", "squeeze", "sales", "webinar", "event"]).optional().default("landing"),
    },
  • Generic toolHandler wrapper that all tools use. For 'maasy_create_landing', it invokes callGateway with toolName='create_landing' and passes the args through directly (no argsFn transformer).
    function toolHandler(toolName: string, argsFn?: (args: Record<string, unknown>) => Record<string, unknown>) {
      return async (args: Record<string, unknown>) => {
        try {
          const gatewayArgs = argsFn ? argsFn(args) : args;
          // Auto-inject default project_id if not provided
          if (DEFAULT_PROJECT_ID && !gatewayArgs.project_id) {
            gatewayArgs.project_id = DEFAULT_PROJECT_ID;
          }
          const result = await callGateway(toolName, gatewayArgs);
          return { content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }] };
        } catch (e: unknown) {
          return {
            content: [{ type: "text" as const, text: `Error: ${e instanceof Error ? e.message : String(e)}` }],
            isError: true,
          };
        }
      };
    }
  • The callGateway function that actually sends the tool request (with toolName='create_landing' and args) as a POST to the mcp-gateway edge function. This is where the actual API call happens.
    export async function callGateway(tool: string, args: Record<string, unknown> = {}): Promise<unknown> {
      const res = await fetch(gatewayUrl, {
        method: "POST",
        headers: {
          "Content-Type": "application/json",
          [authHeader.name]: authHeader.value,
        },
        body: JSON.stringify({ tool, args }),
      });
    
      const data = await res.json();
    
      if (!res.ok) {
        throw new Error(data.error || `Gateway error (${res.status})`);
      }
    
      return data.result;
    }
Behavior2/5

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

With no annotations, the description must disclose all behavioral traits. It only states inputs and outputs, omitting details like persistence, idempotency, required permissions, error handling, or side effects. This is insufficient for a creation tool.

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?

The description is a single, well-structured sentence that front-loads the core purpose and immediately lists return values. Every word is necessary, and there is no redundancy.

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?

The tool has 5 parameters and no output schema, yet the description only covers creation and return types. It lacks context on error handling, slug uniqueness, or prerequisites like project existence. Adequate but incomplete for an agent to use reliably.

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 80%, so the schema already documents most parameters. The description adds marginal value by mentioning 'from HTML' and the return values, but does not elaborate on parameter usage or constraints beyond the schema.

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 explicitly states the action ('Create'), the resource ('landing page in maasy'), the input format ('from HTML'), and the outputs ('landing_id and editor_url'). It clearly distinguishes from sibling tools like maasy_create_skill.

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?

No guidance is provided on when to use this tool versus alternatives, nor are there any usage prerequisites or exclusions mentioned. The description is purely declarative.

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

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/Jbelieve/mcp-server'

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