Skip to main content
Glama
lindoai

mcp-lindoai

Official

update_website_settings

Update website settings by specifying the website ID and a settings object with the desired configuration.

Instructions

Update website settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID
settingsYesSettings object

Implementation Reference

  • The handler function that executes the 'update_website_settings' tool logic. It calls the API endpoint /v1/workspace/website/{website_id}/settings with a PUT request, sending the settings object as the body, and returns the response as formatted JSON text.
    async ({ website_id, settings }) => {
      const data = await apiCall(`/v1/workspace/website/${website_id}/settings`, "PUT", settings);
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Input schema for the 'update_website_settings' tool using Zod. Defines website_id (string) and settings (record of unknown values) parameters.
    {
      website_id: z.string().describe("The website ID"),
      settings: z.record(z.unknown()).describe("Settings object"),
    },
  • Registration of the 'update_website_settings' tool with the MCP server, including name, description, schema, metadata (title, hints), and handler.
    server.tool(
      "update_website_settings",
      "Update website settings.",
      {
        website_id: z.string().describe("The website ID"),
        settings: z.record(z.unknown()).describe("Settings object"),
      },
      { title: "Update Website Settings", readOnlyHint: false, destructiveHint: false, openWorldHint: false },
      async ({ website_id, settings }) => {
        const data = await apiCall(`/v1/workspace/website/${website_id}/settings`, "PUT", settings);
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Helper function used by the tool handler to make authenticated API calls to the Lindo AI backend with Bearer token authorization.
    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();
    }
Behavior2/5

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

Annotations indicate it's not read-only and not destructive, but the description adds no additional behavioral traits (e.g., what settings are affected, whether changes are reversible, or authentication needs). The description provides no value beyond annotations.

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, concise sentence that states the core purpose. It is efficiently trimmed but could benefit from additional structure (e.g., listing example settings).

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?

Despite high schema coverage, the description lacks contextual completeness. It does not explain what 'settings' entails (especially since it's an arbitrary object), nor does it describe return values or effects. The agent has insufficient context to use the tool 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% with both parameters ('website_id' and 'settings') having descriptions. The tool description adds no extra meaning beyond the schema, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update website settings' clearly states the action and resource, but it does not differentiate from sibling tools like 'update_website', which may have overlapping functionality. The description adds no distinction or detail beyond the tool name.

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 (e.g., 'update_website'), nor any exclusions or prerequisites. The agent is left to infer usage from context alone.

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