Skip to main content
Glama

List projects

listProjects

Retrieve projects accessible to your Langfuse API key, typically a single project. Use this tool to identify which project you are working with.

Instructions

List projects accessible to the current API key (typically a single project).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'listProjects' tool. It is registered via server.registerTool with the name 'listProjects', has no input schema, and calls GET /api/public/projects on the Langfuse client, formatting the result as JSON.
    // ---------- Projects ----------
    server.registerTool(
      "listProjects",
      {
        title: "List projects",
        description: "List projects accessible to the current API key (typically a single project).",
        inputSchema: {},
      },
      async () => asJson(await client.get("/api/public/projects")),
    );
  • src/tools.ts:328-337 (registration)
    Registration of the 'listProjects' tool via server.registerTool on lines 329-337. The registerTools function (line 12) is called from src/index.ts (line 59) to wire up all tools.
    // ---------- Projects ----------
    server.registerTool(
      "listProjects",
      {
        title: "List projects",
        description: "List projects accessible to the current API key (typically a single project).",
        inputSchema: {},
      },
      async () => asJson(await client.get("/api/public/projects")),
    );
  • src/tools.ts:392-420 (registration)
    The TOOL_NAMES const array includes 'listProjects' at line 415, used as a type-level list of all tool names for external reference.
    export const TOOL_NAMES = [
      "listTraces",
      "getTrace",
      "listObservations",
      "getObservation",
      "listSessions",
      "getSession",
      "listScores",
      "getScore",
      "listScoreConfigs",
      "getScoreConfig",
      "listPrompts",
      "getPrompt",
      "listDatasets",
      "getDataset",
      "listDatasetItems",
      "getDatasetItem",
      "listDatasetRuns",
      "getDatasetRun",
      "getMetrics",
      "getDailyMetrics",
      "listModels",
      "getModel",
      "listProjects",
      "listComments",
      "getComment",
      "getMedia",
      "getHealth",
    ] as const;
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses that it lists projects based on API key access, implying authentication and read-only behavior. However, no details on rate limits, data freshness, or side effects. Adequate for a simple list.

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 action and resource, no wasted words. Highly concise and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only list tool with no output schema, the description is complete. It tells the agent exactly what to expect: a list of projects accessible to the key.

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 zero parameters, so baseline is 4 per rules. Description adds context about accessibility but no parameter information needed. Schema coverage is 100% (no params to document).

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 action (list), the resource (projects), and scope (accessible to current API key, typically a single project). It distinguishes from sibling list tools.

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 or when not to use it. The description is minimal and doesn't provide context for decision-making.

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/hugoles/langfuse-mcp'

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