Skip to main content
Glama
lindoai

mcp-lindoai

Official

List Websites

list_websites
Read-only

Retrieve a list of all websites within the current workspace. Use this to view available sites before creating or managing pages and content.

Instructions

List all websites in the workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for 'list_websites' tool. Makes a GET request to /v1/workspace/website/list and returns the result as formatted JSON text content.
    async () => {
      const data = await apiCall("/v1/workspace/website/list", "GET");
      return { content: [{ type: "text", text: JSON.stringify(data?.result ?? data, null, 2) }] };
    }
  • Schema definition for 'list_websites'. No inputs required (empty inputSchema), marked as read-only.
    {
      title: "List Websites",
      description: "List all websites in the workspace.",
      inputSchema: {},
      annotations: { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
  • Registration of the 'list_websites' tool via server.registerTool(). All tool logic is inline.
    server.registerTool(
      "list_websites",
      {
        title: "List Websites",
        description: "List all websites in the workspace.",
        inputSchema: {},
        annotations: { readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      },
      async () => {
        const data = await apiCall("/v1/workspace/website/list", "GET");
        return { content: [{ type: "text", text: JSON.stringify(data?.result ?? data, null, 2) }] };
      }
    );
Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. Description adds no further behavioral traits, just restates scope. No contradiction.

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?

Single sentence, front-loaded with verb and resource, efficiently conveying purpose without extraneous words.

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 0 parameters, no output schema, and clear annotations, the description provides adequate completeness for a simple list-all operation, though it could mention typical output traits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0 parameters with 100% coverage; description confirms scope ('all websites in the workspace') adding minimal but sufficient meaning.

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?

Description clearly states the verb 'List' and resource 'websites', and distinguishes it from sibling list tools like list_blogs, list_pages, and other website operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides basic context ('in the workspace') but no guidance on when to use this tool versus alternatives like list_blogs or list_pages, nor any prerequisites or limitations.

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