Skip to main content
Glama
lindoai

mcp-lindoai

Official

list_websites

Read-only

Retrieve a list of all websites in your workspace to manage and review your projects.

Instructions

List all websites in the workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'list_websites' tool via server.tool() with name, description, empty schema, metadata options, and handler function.
    server.tool(
      "list_websites",
      "List all websites in the workspace.",
      {},
      { title: "List Websites", readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      async () => {
        const data = await apiCall("/v1/workspace/website/list", "GET");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • The handler function that calls the API endpoint /v1/workspace/website/list via GET and returns the formatted JSON response.
    async () => {
      const data = await apiCall("/v1/workspace/website/list", "GET");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Helper function used by the handler to make authenticated HTTP requests to the Lindo 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();
    }
  • Empty input schema - the tool takes no parameters.
    {},
Behavior3/5

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

Annotations already indicate readOnlyHint=true, so description's statement 'List all websites' is consistent but adds no further behavioral insight. No mention of pagination, ordering, or output structure.

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 sentence that is front-loaded and concise, with no unnecessary verbiage.

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?

The tool is simple and parameterless, but the description does not specify what is returned (e.g., list of website IDs, names) or any limitations. Minimal but adequate for basic understanding.

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?

There are no parameters, and the schema coverage is 100%. The description adds no extra meaning beyond the schema, which is acceptable for a parameterless tool.

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 verb (list) and resource (websites) with scope (all in workspace). It effectively distinguishes itself from sibling tools like get_website, create_website, etc.

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 such as get_website for a single website. The description lacks context for proper selection among many similar tools.

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