mcp-fabric-api

pipeline_update_definition

Update a data pipeline's definition by reading definition files from a specified directory. Provide workspace, pipeline, and directory path to apply changes.

Instructions

Update a data pipeline's definition (long-running). Reads definition files from the specified directory.

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>",
      "definitionDirectoryPath": "<definitionDirectoryPath>"
    },
    "name": "pipeline_update_definition"
  }
}

Input Schema

Name	Required	Description
`pipelineId`	Yes	The pipeline ID
`workspaceId`	Yes	The workspace ID
`definitionDirectoryPath`	Yes	Path to a directory containing pipeline definition files

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already indicate this is not read-only and not destructive. The description adds the useful behavioral detail that the operation is long-running and reads definition files from a directory, but it does not disclose what happens to the existing definition, whether the operation is asynchronous, or how to track its completion.

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 concise sentence that front-loads the primary action and adds the key behavioral note about long-running execution. There is no filler or redundancy.

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

Completeness2/5

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

There is no output schema, and the description does not explain what the caller receives, whether the operation is asynchronous, or how to monitor progress despite calling it 'long-running'. It also does not specify the expected format or contents of the definition files, leaving important invocation context unclear.

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 all three parameters already documented. The description adds no additional format, constraint, or relationship information beyond what the schema provides, so it stays at the baseline.

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

Purpose4/5

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

The description states a specific verb ('Update') and resource ('a data pipeline's definition'), and the phrase 'Reads definition files from the specified directory' clarifies the mechanism. It is distinguishable from related tools like pipeline_update or pipeline_get_definition, though it does not explicitly name a sibling for contrast.

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 gives no guidance on when to use this tool versus alternatives such as pipeline_update, pipeline_get_definition, or other update_definition tools. It implies a file-based definition update but does not state conditions, exclusions, or prerequisites.

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

Deploy Server