Skip to main content
Glama

liara_add_domain

Add a custom domain to your Liara cloud application to enable public access with your own domain name.

Instructions

Add a domain to an app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNameYesThe name of the app
domainYesDomain name to add

Implementation Reference

  • The main handler function implementing the logic to add a domain to a Liara app. It performs input validation and calls the Liara API to add the domain.
    export async function addDomain(
        client: LiaraClient,
        appName: string,
        domain: string
    ): Promise<Domain> {
        validateRequired(appName, 'App name');
        validateRequired(domain, 'Domain');
    
        return await client.post<Domain>('/v1/domains', {
            project: appName,
            domain,
        });
    }
  • Type definition for the Domain object returned by the addDomain API call, serving as the output schema for the tool.
    export interface Domain {
        _id: string;
        name: string;
        projectID: string;
        status: DomainStatus;
        createdAt: string;
    }
  • Imports validation helpers used in the handler.
    import { validateRequired, unwrapApiResponse } from '../utils/errors.js';
  • Validation helper used to check required inputs in the handler. (Assuming approximate lines based on usage; actual may vary)
    if (name.length < 3) {
        throw new LiaraMcpError(
            `App name "${name}" is too short (minimum 3 characters, got ${name.length})`,
            'INVALID_APP_NAME',
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention whether this requires specific permissions, if it's idempotent, what happens on conflicts, or any rate limits—critical for a mutation tool with zero annotation coverage.

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, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on permissions, error conditions, return values, or how it interacts with sibling domain tools, leaving significant gaps for an agent to use it correctly.

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 both parameters ('appName' and 'domain') adequately. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, meeting the baseline for high schema coverage.

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 action ('Add') and resource ('a domain to an app'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'liara_set_default_subdomain' or 'liara_remove_domain' that also operate on domains, missing explicit sibling distinction.

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. The description doesn't mention prerequisites, constraints, or when to choose this over similar tools like 'liara_set_default_subdomain' for domain management, leaving usage context implied at best.

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/razavioo/liara-mcp'

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