Skip to main content
Glama
avivsinai

langfuse-mcp

list_datasets

Retrieve paginated datasets from Langfuse projects to view metadata like name, description, item count, and timestamps.

Instructions

List all datasets in the project with pagination.

Returns metadata about datasets including name, description, item count, and timestamps.

Args:
    ctx: Context object containing lifespan context with Langfuse client
    page: Page number for pagination (starts at 1)
    limit: Maximum items per page (max 100)

Returns:
    A dictionary containing:
    - data: List of dataset metadata objects
    - metadata: Pagination info (page, limit, total)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (starts at 1)
limitNoItems per page (max 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses pagination behavior and return format, which is helpful. However, it doesn't mention authentication requirements, rate limits, error conditions, or whether this is a read-only operation (though 'List' implies reading).

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 well-structured with clear sections (purpose, returns, args, returns details) and appropriately sized. However, the parameter documentation section is redundant with the schema and could be more concise.

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?

For a list operation with full schema coverage and an output schema, the description provides adequate context about what's returned and how pagination works. The main gap is lack of guidance on when to use this versus sibling tools.

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%, so the schema already fully documents both parameters. The description repeats the same parameter information without adding additional context about default behaviors or edge cases beyond what's in the schema.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'List all datasets in the project with pagination.' It specifies the verb ('List'), resource ('datasets'), and scope ('in the project'), but doesn't explicitly differentiate from sibling tools like 'get_dataset' or 'list_dataset_items'.

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 like 'get_dataset' (for single dataset details) or 'list_dataset_items' (for items within datasets). The description only states what the tool does, not when it's appropriate.

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/avivsinai/landfuse-mcp'

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