Skip to main content
Glama
lindoai

mcp-lindoai

Official

delete_website

Destructive

Remove a website from your workspace by providing its record ID.

Instructions

Delete a website from the workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
record_idYesWebsite record ID to delete

Implementation Reference

  • The handler function for the 'delete_website' tool. It calls the API endpoint /v1/workspace/website/delete with a DELETE method and the record_id parameter.
    async ({ record_id }) => {
      const data = await apiCall("/v1/workspace/website/delete", "DELETE", { record_id });
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Input schema for the 'delete_website' tool. Accepts a single string parameter 'record_id' describing the website record ID to delete.
    {
      record_id: z.string().describe("Website record ID to delete"),
    },
  • Registration of the 'delete_website' tool using server.tool() with the name 'delete_website', a description, schema, metadata, and handler function.
    server.tool(
      "delete_website",
      "Delete a website from the workspace.",
      {
        record_id: z.string().describe("Website record ID to delete"),
      },
      { title: "Delete Website", readOnlyHint: false, destructiveHint: true, openWorldHint: false },
      async ({ record_id }) => {
        const data = await apiCall("/v1/workspace/website/delete", "DELETE", { record_id });
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • The apiCall helper function used by the delete_website handler to make HTTP requests to the Lindo AI API.
    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?

The description confirms the destructive nature ('Delete'), which aligns with annotations (destructiveHint=true). However, it adds no additional behavioral context beyond what annotations already provide. No contradictions.

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 a single, clear sentence with no extraneous words. It is concise and front-loaded, though it could include slightly more detail without becoming verbose.

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?

For a simple delete tool with one parameter and no output schema, the description is adequate but lacks mention of return values or what happens after deletion (e.g., confirmation or effects). More context would improve completeness.

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?

Input schema coverage is 100% and already describes the parameter ('Website record ID to delete'). The description adds no further meaning beyond the schema, so the baseline of 3 is appropriate.

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 'Delete a website from the workspace.' It uses a specific verb ('Delete') and resource ('website'), distinguishing it from sibling tools like delete_blog, delete_client, and delete_page. The purpose is unambiguous.

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 vs alternatives, when not to use it, or any prerequisites. It simply states the action without offering any usage context.

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