Skip to main content
Glama
lindoai

mcp-lindoai

Official

update_website

Update a website record by providing its ID, then modify the business name or description as needed.

Instructions

Update website details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
record_idYesWebsite record ID
business_nameNoBusiness name
business_descriptionNoBusiness description

Implementation Reference

  • The 'update_website' tool handler. It accepts record_id (required), business_name (optional), and business_description (optional), then sends a PATCH request to /v1/workspace/website/update with the provided fields.
    server.tool(
      "update_website",
      "Update website details.",
      {
        record_id: z.string().describe("Website record ID"),
        business_name: z.string().optional().describe("Business name"),
        business_description: z.string().optional().describe("Business description"),
      },
      { title: "Update Website", readOnlyHint: false, destructiveHint: false, openWorldHint: false },
      async ({ record_id, business_name, business_description }) => {
        const body = { record_id };
        if (business_name) body.business_name = business_name;
        if (business_description) body.business_description = business_description;
        const data = await apiCall("/v1/workspace/website/update", "PATCH", body);
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • The 'update_website' tool is registered via server.tool() with all its schema, options, and handler inline.
    server.tool(
      "update_website",
      "Update website details.",
      {
        record_id: z.string().describe("Website record ID"),
        business_name: z.string().optional().describe("Business name"),
        business_description: z.string().optional().describe("Business description"),
      },
      { title: "Update Website", readOnlyHint: false, destructiveHint: false, openWorldHint: false },
      async ({ record_id, business_name, business_description }) => {
        const body = { record_id };
        if (business_name) body.business_name = business_name;
        if (business_description) body.business_description = business_description;
        const data = await apiCall("/v1/workspace/website/update", "PATCH", body);
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Input schema for 'update_website': record_id (string, required), business_name (string, optional), business_description (string, optional).
    {
      record_id: z.string().describe("Website record ID"),
      business_name: z.string().optional().describe("Business name"),
      business_description: z.string().optional().describe("Business description"),
    },
  • The apiCall helper function that sends authenticated HTTP requests to the Lindo AI API. Used by the handler to make the PATCH request.
    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 readOnlyHint=false and destructiveHint=false. Description adds no additional behavioral context beyond stating it's an update operation.

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 extremely concise with one short sentence. No wasted words, but could be more informative.

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?

The description is minimal for a tool with 3 parameters and no output schema. It does not explain what the tool returns or handling of non-existent record_id, making it insufficient for confident use.

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 has 100% coverage with descriptions for all parameters. The description does not add any additional meaning beyond the schema.

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 it updates website details, identifying verb+resource. However, it does not differentiate from sibling tool 'update_website_settings', which could cause confusion.

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 like 'update_website_settings'. No mention of prerequisites or exclusions.

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