Skip to main content
Glama
syucream

Lightdash MCP Server

by syucream

lightdash_list_projects

Retrieve a complete list of all projects within your Lightdash organization to manage and navigate analytics workspaces.

Instructions

List all projects in the Lightdash organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the lightdash_list_projects tool. Calls GET /api/v1/org/projects on the Lightdash API and returns the results as JSON text.
    case 'lightdash_list_projects': {
      const { data, error } = await lightdashClient.GET(
        '/api/v1/org/projects',
        {}
      );
      if (error) {
        throw new Error(
          `Lightdash API error: ${error.error.name}, ${
            error.error.message ?? 'no message'
          }`
        );
      }
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(data.results, null, 2),
          },
        ],
      };
    }
  • src/mcp.ts:49-53 (registration)
    Registration of the lightdash_list_projects tool in the ListTools handlers, defining its name, description, and input schema.
    {
      name: 'lightdash_list_projects',
      description: 'List all projects in the Lightdash organization',
      inputSchema: zodToJsonSchema(ListProjectsRequestSchema),
    },
  • Schema definition for the lightdash_list_projects tool input - an empty object (no required parameters).
    export const ListProjectsRequestSchema = z.object({});
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only states the action without revealing any behavioral traits such as whether pagination occurs, authentication requirements, or potential side effects. For a list operation, additional context like response format is missing.

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 with no redundant words. It is front-loaded and efficient.

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 with no parameters and no output schema. The description is sparse but sufficient for a basic listing operation. It could be improved by mentioning the expected output structure (e.g., 'returns an array of project summaries').

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?

There are zero parameters, and the input schema has 100% coverage. The description adds no parameter information, but none is needed. Baseline for no parameters is 4.

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 the resource 'projects', with the scope 'in the Lightdash organization'. This distinguishes it from sibling tools like 'lightdash_get_project' (singular) and other list operations for different resources.

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?

The description implies use for listing all projects, but it doesn't explicitly state when to use or when not to use, nor does it mention alternatives. Since no sibling tool directly competes, the guidance is adequate but not detailed.

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/syucream/lightdash-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server