mcp-fabric-api

pipeline_update

Update a Microsoft Fabric pipeline's display name or description by providing the workspace and pipeline IDs.

Instructions

Update a pipeline's name or description

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_update"
  }
}

Input Schema

Name	Required	Description
`pipelineId`	Yes	The pipeline ID
`description`	No	New description
`displayName`	No	New display name
`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 communicate that this is a mutating but non-destructive operation. The description adds no further behavioral context, such as whether the update is partial, whether old values are replaced, or what permissions are needed. It does not contradict the annotations.

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?

A single, front-loaded sentence with no filler. Every word contributes to understanding the tool's purpose and scope.

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 simple metadata-update tool with fully documented parameters and safety annotations, the description is nearly complete. It could mention the effect on existing values or the return behavior, but those are not critical for correct invocation.

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%, so the schema already documents all parameters. The description loosely maps 'name or description' to displayName and description, but adds no extra semantic detail beyond what is already present.

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 identifies the verb ('Update'), the resource ('pipeline'), and the specific scope ('name or description'). This distinguishes it from sibling tools like pipeline_update_definition and pipeline_update_schedule, so an agent can confidently select it for metadata changes.

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 states what the tool does but provides no guidance on when to use it versus alternatives. It does not mention that pipeline_update_definition should be used for definition changes or pipeline_update_schedule for schedule changes, leaving the agent to infer the appropriate context.

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

Deploy Server