Skip to main content
Glama
avivsinai

langfuse-mcp

list_datasets

Retrieve a paginated list of datasets in your Langfuse project, including metadata such as 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?

No annotations exist, so description must disclose behavior. It accurately states it returns metadata and pagination info, but lacks details on side effects, rate limits, or authentication. Adequate for a read operation.

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?

Concise with a clear opening sentence, docstring-style args, and return structure. No unnecessary words, well-organized.

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?

Description explains return structure (data and metadata), which is sufficient given the output schema exists. Could mention that pagination starts at 1, but that's in schema. Overall complete.

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 coverage is 100%; description repeats parameter details already in schema. No additional semantics or constraints added beyond what schema provides.

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?

Clearly states 'List all datasets in the project with pagination,' specifying the verb, resource, and scope. Distinguishes from siblings like 'get_dataset' and 'create_dataset'.

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?

Does not provide when-to-use or when-not-to-use guidance. No mention of alternatives like 'get_dataset' for specific datasets or pagination best practices.

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