Skip to main content
Glama
ChrisChoTW

databricks-mcp

by ChrisChoTW

list_job_runs

Retrieve the execution history of a Databricks job to monitor its performance and track past runs for analysis.

Instructions

List job run history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the list_job_runs MCP tool which fetches job run history for a given job_id.
    def list_job_runs(ctx: Context, job_id: int, limit: int = 10) -> List[Dict[str, Any]]:
        """List job run history"""
        w = get_workspace_client()
        runs_iter = w.jobs.list_runs(job_id=job_id, expand_tasks=False)
        results = []
        for i, run in enumerate(runs_iter):
            if i >= limit:
                break
            run_d = run.as_dict()
            results.append({
                "run_id": run_d.get("run_id"),
                "job_id": run_d.get("job_id"),
                "state": run_d.get("state"),
                "start_time": run_d.get("start_time"),
                "end_time": run_d.get("end_time"),
                "run_page_url": run_d.get("run_page_url")
            })
        return results
Behavior2/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. 'List job run history' implies a read-only operation but doesn't specify permissions needed, pagination behavior, rate limits, or what constitutes 'history' (time range, status filters). For a tool with zero annotation coverage, this is insufficient.

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 extremely concise at just three words. While this brevity comes at the cost of completeness, every word earns its place - 'List' specifies the action, 'job run' specifies the resource, and 'history' adds temporal context.

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

Completeness3/5

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

Given the tool has an output schema (which handles return values), the description's minimalism is somewhat acceptable. However, with 2 parameters (one required), 0% schema coverage, and no annotations, the description should do more to explain parameter meaning and behavioral context for a listing operation.

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

Parameters2/5

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

Schema description coverage is 0%, meaning neither parameter has documentation in the schema. The description provides no information about what 'job_id' refers to (what jobs, where they come from) or what 'limit' controls (number of runs, time range). It fails to compensate for the complete lack of schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List job run history' clearly states the verb ('List') and resource ('job run history'), making the basic purpose understandable. However, it doesn't distinguish this tool from potential siblings like 'get_job_run' or 'list_jobs' - it's vague about scope and differentiation.

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. With siblings like 'get_job_run' (singular) and 'list_jobs' (jobs rather than runs), there's clear potential for confusion, but the description offers no help in choosing between them.

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/ChrisChoTW/databricks-mcp'

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