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;
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns a landing_id and editor_url, which is a useful outcome, but it does not mention any other behavioral traits like authentication requirements, side effects, or whether the operation is reversible.

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 two short sentences, front-loaded with the action and resource, with no wasted words.

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 description covers the basic action and return values but lacks any usage guidance or behavioral details beyond creation. Given the moderate complexity (5 params, no annotations), this is a minimal but not comprehensive description.

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 coverage is 80%, and the schema already describes most parameters. The description only reinforces that HTML is the input source, adding little beyond the schema. The type enum and project_id are left to schema documentation.

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 uses the specific verb 'Create' with the resource 'landing page' and the source 'from HTML', clearly distinguishing it from other maasy creation tools. It also states the output (landing_id and editor_url), making the purpose unmistakable.

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 gives no guidance on when to use this tool versus alternatives, and no mention of prerequisites or exclusions. It simply states what the tool does without contextualizing it among the sibling tools.

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