Skip to main content
Glama
Sign In
Copilot Studio MCP

Copilot Studio MCP

by jgt87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Deploy through a Power Platform pipeline

cs_deploy_pipeline

Start a pipeline deployment of a solution to a Power Platform pipeline stage; set confirm: true to apply changes, or omit it for a dry run.

Instructions

Start a pipeline deployment of a solution to a stage (the alternative to cs_deploy_solution when the tenant uses Power Platform pipelines). stageId comes from cs_list_pipelines. Runs 'pac pipeline deploy' with the active pac auth profile. Mutates a live environment: requires confirm: true (a dry run otherwise).

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": {
      "solutionName": "<solutionName>",
      "stageId": "<stageId>",
      "currentVersion": "<currentVersion>",
      "newVersion": "<newVersion>"
    },
    "name": "cs_deploy_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoWorking directory for pac (for project commands: the solution project folder)
waitNoWait until the deployment finishes
confirmNoRequired to actually perform a change in a live environment. Without it the tool returns a dry run.
profileNopac auth profile to run as: the admin account for tenant commands. Defaults to CPS_ADMIN_PROFILE for admin commands and CPS_PAC_PROFILE otherwise, then the active profile. cs_init lists the profiles.
stageIdYesDeployment stage id (cs_list_pipelines with pipeline)
backgroundNoRun in the background and return a jobId immediately, for a command that takes longer than the client will wait. Poll cs_job_status.
newVersionYesVersion to deploy as
environmentNoEnvironment id or URL; default: the environment of the active pac auth profile
solutionNameYesSolution unique name
currentVersionYesCurrent solution version
timeoutSecondsNoDefault 3600

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.8
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.5

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool mutates a live environment, that confirm: true is required with a dry run otherwise, and that it runs 'pac pipeline deploy' with the active pac auth profile. It does not cover failure/rollback behavior or permission boundaries beyond the active profile, so it is not fully complete.

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?

Four tightly written sentences, front-loaded with the action and the safety-critical confirm requirement. Every sentence adds distinct value with no wasted text.

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 an 11-parameter mutation tool with no annotations and no output schema, the description covers purpose, alternative, stage source, and the safety gate. It omits behavioral details such as wait/background polling and failure handling, which keeps it from being fully complete.

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 baseline is 3. The description reinforces stageId's source and the confirm/dry-run semantics, but these are already documented in the schema; it adds no new format or constraint details beyond structured fields.

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?

States a specific verb and resource: 'Start a pipeline deployment of a solution to a stage.' It explicitly distinguishes itself from the sibling cs_deploy_solution by naming the tenant condition that selects it, so an agent can choose without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative tool cs_deploy_solution and the condition for using this one (tenant uses Power Platform pipelines). It also points to cs_list_pipelines as the source of stageId, leaving no ambiguity about when and how to use it.

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