Skip to main content
Glama
Sign In
Microsoft Fabric MCP Server

Microsoft Fabric MCP Server

by og-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

fabric_create_pipeline

Create data pipelines in Microsoft Fabric with optional activities and parameters for automated data processing.

Instructions

Create a data pipeline, optionally with activities + parameters.

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": {
      "displayName": "<displayName>"
    },
    "name": "fabric_create_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
displayNameYesPipeline name
descriptionNo
activitiesNoADF-format activity objects (TridentNotebook, Copy, …)
parametersNoPipeline parameters (name → { type, defaultValue })
workspaceNoWorkspace ID (defaults to FABRIC_DEFAULT_WORKSPACE)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Create', implying a mutating operation, but omits important traits such as idempotency, overwrite behavior, authentication needs, or side effects (e.g., whether it triggers any processes). The agent has very limited insight into the tool's runtime behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, very concise at 10 words. It immediately states the core action. However, it could be considered too brief for a tool with 5 parameters and nested objects; a slightly expanded structure (e.g., mentioning the typical use case) would earn a 5. Still, no wasted words.

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?

Given the tool's complexity (5 parameters, nested objects, no output schema, no annotations), the description is insufficient. It fails to explain what happens after creation (e.g., returns pipeline ID or object), error handling, or the role of the workspace parameter. The high schema coverage helps, but the description does not fill contextual gaps.

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 80%, so the schema already documents most parameters well. The description adds 'optionally with activities + parameters', which hints that two parameters are optional (already implied by schema not listing them as required). It does not add meaning beyond what the schema provides, meeting the baseline of 3.

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 tool's purpose: 'Create a data pipeline'. The verb is specific ('Create'), and the resource is 'data pipeline'. The optional addition of 'with activities + parameters' hints at the scope. The tool's name includes 'pipeline', and sibling tools create other resources (dataflows, eventhouses, etc.), so differentiation is implicit but clear.

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. For example, it doesn't distinguish between creating a new pipeline and updating one (fabric_update_pipeline_definition). No prerequisites, workspace requirements, or when-not-to-use scenarios are mentioned. The agent must infer from the tool name alone.

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

Deploy Server

Other Tools