Skip to main content
Glama
Log-LogN

langfuse-mcp-java

get_exception_details

Inspect specific error traces in Langfuse by retrieving full details including nested observations, input/output, metadata, and timing for debugging LLM application failures.

Instructions

Returns the full detail of a single ERROR-level trace identified by its ID.

Equivalent to fetch_trace but semantically scoped to error traces. Use this after find_exceptions to inspect a specific failure in depth — the response includes all nested observations, input/output, metadata, and timing.

The traceId is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
traceIdYesThe Langfuse trace ID (UUID) of the error trace to inspect. Required — the call will be rejected if this is missing or blank.

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/Log-LogN/langfuse-mcp-java'

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