Skip to main content
Glama
KarandeepSinghSodhi

Langfuse Trace Fetcher

fetch_langfuse_traces

Fetch filtered traces from Langfuse by providing API credentials and optional filters like name, tags, user ID, or time range.

Instructions

Fetch a filtered list of traces from a Langfuse instance.

Connects to the specified Langfuse host using the provided credentials and returns matching traces formatted as readable context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter by trace name.
pageNoPage number for pagination (default 1).
tagsNoFilter by tags (traces must have ALL specified tags).
limitNoMax number of traces to return (1–100, default 20).
releaseNoFilter by release identifier.
user_idNoFilter by user ID.
versionNoFilter by application version.
host_urlYesLangfuse host URL (e.g. https://cloud.langfuse.com or http://localhost:3000).
public_keyYesLangfuse public API key.
secret_keyYesLangfuse secret API key.
session_idNoFilter by session ID.
environmentNoFilter by environment (e.g. production, staging).
to_timestampNoISO 8601 end time — only return traces before this time.
from_timestampNoISO 8601 start time — only return traces at or after this time.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries full burden. It states that the tool 'connects...using provided credentials' and 'returns...matching traces formatted as readable context', implying a read operation. However, it does not disclose details like rate limits, error behaviors, or any side effects, leaving gaps.

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 only two sentences, free of redundancy, and every sentence adds value. It is concise and front-loaded with the key purpose.

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 the 14 parameters with full schema descriptions and the presence of an output schema, the description is reasonably complete. It could mention pagination or filtering behavior, but the schema and output schema fill in many gaps.

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%, so the baseline is 3. The description adds no extra meaning beyond 'filtered list', and all parameter details are already in the schema. The description does not enrich parameter understanding.

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 'Fetch a filtered list of traces from a Langfuse instance', specifying the verb and resource. While it distinguishes from sibling tools by name, it does not explicitly contrast with 'get_langfuse_trace_detail' or 'list_langfuse_trace_filters'.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'get_langfuse_trace_detail' (for a single trace) or 'list_langfuse_trace_filters' (to list available filters). There are no when-not-to-use or prerequisite instructions.

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/KarandeepSinghSodhi/Skill-to-fetch-traces'

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