mcp-fabric-api

pipeline_list_runs

Read-only

Retrieve all run instances for a specific pipeline in a Fabric workspace using the pipeline and workspace IDs.

Instructions

List all run instances for a pipeline

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceId": "<workspaceId>",
      "pipelineId": "<pipelineId>"
    },
    "name": "pipeline_list_runs"
  }
}

Input Schema

Name	Required	Description	Default
`pipelineId`	Yes	The pipeline ID
`workspaceId`	Yes	The workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the scoping detail 'for a pipeline' and the breadth of 'all run instances', but it does not disclose pagination, ordering, or what fields are returned.

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 a single, focused sentence with no filler. It front-loads the action and resource, and every word contributes to meaning.

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

Completeness4/5

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

For a low-complexity tool with two required, fully documented parameters and read-only annotations, the description is sufficient for an agent to select and invoke it correctly. The absence of an output schema is partially mitigated by the clear 'list all run instances' phrasing, though return format or pagination details would improve completeness.

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

Parameters3/5

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

Schema description coverage is 100%, with both pipelineId and workspaceId already described in the input schema. The tool description adds no parameter-level information beyond that, so the baseline 3 applies.

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 uses the specific verb 'List' with the resource 'run instances' and the scope 'for a pipeline', making it immediately distinct from sibling tools like pipeline_list (which lists pipelines) and pipeline_get (which fetches a single pipeline). An agent can identify what this tool does without inspecting the schema.

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 such as pipeline_get_run_status, pipeline_list_schedules, or copy_job_list_runs. The intended use case is only implied by the name and phrasing, not explicitly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server