mcp-fabric-api

environment_publish

Trigger a Microsoft Fabric environment publish to apply staging changes. Provide workspace ID and environment ID to start the long-running operation.

Instructions

Trigger an environment publish to make staging changes effective (long-running)

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>",
      "environmentId": "<environmentId>"
    },
    "name": "environment_publish"
  }
}

Input Schema

Name	Required	Description	Default
`workspaceId`	Yes	The workspace ID
`environmentId`	Yes	The environment ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already indicate this is a mutating but non-destructive operation. The description adds the useful behavioral trait that the operation is 'long-running', but does not disclose what the response looks like, whether the call is asynchronous, or how cancellation might be handled.

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 conveys the action, purpose, and an important operational nuance ('long-running') with no filler or redundancy.

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?

The core invocation details are present and the two required parameters are fully described in the schema. However, with no output schema, the description does not clarify the return value, operation status handling, or how this interacts with environment_cancel_publish for a long-running operation.

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 coverage is 100%: both workspaceId and environmentId are documented in the input schema. The description adds no parameter-level detail, so the baseline of 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 states a specific action ('Trigger an environment publish') and the precise outcome ('make staging changes effective'). This clearly distinguishes it from environment_cancel_publish and other environment_* tools without needing to inspect schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a clear context for when to use the tool: when staging changes need to take effect. It does not explicitly mention exclusions or name alternatives like environment_cancel_publish, but the trigger condition is unambiguous.

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

Deploy Server