Skip to main content
Glama

List Notebook Executions

list_notebook_executions

Retrieve execution history for a Microsoft Fabric notebook to view past job instances, states, and timing information for analysis and troubleshooting.

Instructions

List all Livy sessions (execution history) for a notebook.

Retrieves a list of all Livy sessions associated with a notebook, providing an execution history with job instance IDs, states, and timing information.

Use this tool when:

  • You want to see the execution history of a notebook

  • You need to find a job instance ID for a past execution

  • You want to analyze execution patterns over time

Parameters: workspace_name: The display name of the workspace containing the notebook. notebook_name: Name of the notebook. limit: Optional maximum number of sessions to return.

Returns: Dictionary with: - status: "success" or "error" - message: Description of the result - sessions: List of session summaries, each containing: - job_instance_id: Unique identifier for the job - livy_id: Livy session identifier - state: Execution state (Success, Failed, Cancelled, etc.) - operation_name: Type of operation (Notebook Scheduled Run, etc.) - spark_application_id: Spark application identifier - submitted_time_utc: When the job was submitted - start_time_utc: When execution started - end_time_utc: When execution ended - total_duration_seconds: Total execution time - total_count: Total number of sessions found

Example: ```python history = list_notebook_executions( workspace_name="Analytics", notebook_name="ETL_Pipeline", limit=10 )

if history["status"] == "success":
    print(f"Found {history['total_count']} executions")
    for session in history["sessions"]:
        print(f"{session['job_instance_id']}: {session['state']}")
```

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_nameYes
notebook_nameYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes what the tool does (retrieves execution history), what information it provides (job instance IDs, states, timing), and includes a detailed return structure. However, it doesn't mention potential limitations like pagination, rate limits, or authentication requirements, which would be helpful for a production tool.

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: purpose statement, usage guidelines, parameters, returns, and example. Every sentence earns its place by providing essential information. The front-loaded purpose statement immediately tells users what the tool does, followed by progressively detailed information.

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 (3 parameters, no annotations, but has output schema), the description is remarkably complete. It covers purpose, usage guidelines, parameter semantics, and includes a detailed return structure with example. The output schema existence means the description doesn't need to explain return values in detail, but it still provides a comprehensive overview that would help an agent use the tool correctly.

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 0%, so the description must compensate. It provides clear explanations for all three parameters: workspace_name ('display name of the workspace'), notebook_name ('Name of the notebook'), and limit ('Optional maximum number of sessions to return'). This adds significant value beyond the bare schema, though it doesn't specify format constraints or examples for workspace/notebook names.

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 specific verb ('List all Livy sessions') and resource ('for a notebook'), with additional context about execution history. It distinguishes this tool from siblings like 'get_notebook_execution_details' (which likely provides details for a single execution) and 'livy_list_sessions' (which appears to list all Livy sessions without notebook filtering).

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 description includes an explicit 'Use this tool when:' section with three specific scenarios: seeing execution history, finding job instance IDs, and analyzing execution patterns. This provides clear guidance on when to use this tool versus alternatives like 'get_notebook_execution_details' for detailed information about a specific execution.

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/bablulawrence/ms-fabric-mcp-server'

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