Schema | Langfuse Trace Fetcher

Langfuse Trace Fetcher

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }
`logging`	{}
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`extensions`	{ "io.modelcontextprotocol/ui": {} }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
fetch_langfuse_tracesB	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.
get_langfuse_trace_detailA	Fetch full detail for a single Langfuse trace by its ID. Returns the complete trace including input/output data, observations (spans, generations), scores, and metadata.
list_langfuse_trace_filtersA	List all available filter fields for fetching Langfuse traces. This is a help/reference tool — it does not make any API calls. Use these filter names as parameters when calling fetch_langfuse_traces. Returns: A formatted reference table of available filters.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

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