Skip to main content
Glama
lindoai

mcp-lindoai

Official

remove_custom_domain

Destructive

Remove a custom domain from a website by providing the website ID.

Instructions

Remove a custom domain from a website.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID

Implementation Reference

  • Tool registration for 'remove_custom_domain' using server.tool() with name, description, schema, options, and handler.
    server.tool(
      "remove_custom_domain",
      "Remove a custom domain from a website.",
      {
        website_id: z.string().describe("The website ID"),
      },
      { title: "Remove Custom Domain", readOnlyHint: false, destructiveHint: true, openWorldHint: false },
      async ({ website_id }) => {
        const data = await apiCall(`/v1/workspace/website/${website_id}/domain`, "DELETE");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Input schema for remove_custom_domain: requires website_id (string).
    {
      website_id: z.string().describe("The website ID"),
    },
  • Handler function: makes DELETE API call to /v1/workspace/website/{website_id}/domain and returns the JSON result.
    { title: "Remove Custom Domain", readOnlyHint: false, destructiveHint: true, openWorldHint: false },
    async ({ website_id }) => {
      const data = await apiCall(`/v1/workspace/website/${website_id}/domain`, "DELETE");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Helper apiCall function that performs authenticated HTTP requests using the API key.
    async function apiCall(path, method, body) {
      const url = `${BASE_URL}${path}`;
      const res = await fetch(url, {
        method,
        headers: {
          Authorization: `Bearer ${API_KEY}`,
          "Content-Type": "application/json",
        },
        ...(body ? { body: JSON.stringify(body) } : {}),
      });
      return res.json();
    }
Behavior3/5

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

Annotations already indicate destructiveHint=true, so the agent knows this is destructive. The description confirms the action but adds no additional behavioral context beyond what annotations provide, such as side effects or permissions required.

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 one short sentence with no wasted words. It is appropriately sized for a simple destructive action.

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?

Given the tool's simplicity (one parameter, no output schema, destructive) and the presence of explicit annotations, the description is adequate. However, it could mention that the domain removal is immediate or permanent to add more context.

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 has 100% description coverage for the single parameter 'website_id', so the description adds no extra info. The baseline score of 3 is appropriate as the schema already explains the parameter well.

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 clearly states the action 'Remove' and the resource 'custom domain from a website', with a specific verb and resource. It distinguishes this tool from its sibling 'add_custom_domain'.

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 on when to use this tool vs alternatives. There is no mention of prerequisites, when not to use, or that removal is irreversible. The description lacks context for decision-making.

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

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