Skip to main content
Glama
avivsinai

langfuse-mcp

get_user_sessions

Retrieve user sessions from Langfuse within a specified time range to analyze LLM application interactions, with options for detailed observation data and output formats.

Instructions

Get sessions for a user within a time range.

Args:
    ctx: Context object containing lifespan context with Langfuse client
    user_id: The ID of the user to retrieve sessions for (unique identifier string)
    age: Minutes ago to start looking (e.g., 1440 for 24 hours)
    include_observations: If True, fetch and include the full observation objects instead of just IDs.
        Use this when you need access to system prompts, model parameters, or other details stored
        within observations. Significantly increases response time but provides complete data.
    output_mode: Controls the output format and detail level

Returns:
    Based on output_mode:
    - compact: List of summarized session objects
    - full_json_string: String containing the full JSON response
    - full_json_file: List of summarized session objects with file save info

Usage Tips:
    - For quick browsing: use include_observations=False with output_mode="compact"
    - For full data but viewable in responses: use include_observations=True with output_mode="compact"
    - For complete data dumps: use include_observations=True with output_mode="full_json_file"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesThe ID of the user to retrieve sessions for
ageYesMinutes ago to start looking (e.g., 1440 for 24 hours)
include_observationsNoIf True, fetch and include the full observation objects instead of just IDs. Use this when you need access to system prompts, model parameters, or other details stored within observations. Significantly increases response time but provides complete data. Pairs well with output_mode='full_json_file' for complete dumps.
output_modeNoControls the output format and action. 'compact' (default): Returns a summarized JSON object optimized for direct agent consumption. 'full_json_string': Returns the complete, raw JSON data serialized as a string. 'full_json_file': Returns a summarized JSON object AND saves the complete data to a file.compact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it explains that include_observations 'significantly increases response time' (performance impact), describes what each output_mode does (format and file-saving behavior), and clarifies data completeness trade-offs. It doesn't mention authentication or rate limits, but covers most operational aspects.

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 well-structured with clear sections (Args, Returns, Usage Tips), front-loads the core purpose, and every sentence adds value—no redundant information. The Usage Tips provide actionable guidance without verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (4 parameters, time-based filtering, output format options) and the presence of an output schema (which handles return value documentation), the description is complete: it covers purpose, parameter semantics, behavioral trade-offs, and usage guidelines. No significant gaps remain for agent understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds value by explaining the practical implications of include_observations ('when you need access to system prompts...') and providing concrete usage examples in the Tips section that clarify how parameters interact. However, it doesn't fully explain the 'ctx' parameter beyond stating it contains context.

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?

The description clearly states the verb ('Get') and resource ('sessions for a user within a time range'), distinguishing it from sibling tools like 'fetch_sessions' (which likely fetches all sessions without user filtering) and 'get_session_details' (which likely gets details for a specific session). The purpose is specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Usage Tips' section provides explicit guidance on when to use different parameter combinations for specific scenarios (quick browsing, full data viewable in responses, complete data dumps). It also implicitly distinguishes from siblings by focusing on user-specific sessions with time filtering, unlike broader fetch tools.

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