Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

publish_ribbon_solution

Destructive

Publishes accepted Ribbon customizations to Dataverse after an authenticated import receipt, with dry-run and explicit full-table/write flags. Use separate Web Resource publication.

Instructions

Separate preview/publish after a same-process authenticated import receipt, matching native succeeded import job and successful bounded manifest log. Check current target/exportable non-Ribbon baseline, CSDL and effective Ribbon before native PublishXml. Execute with planHash, allow_unprotected_write and allow_full_table_publish. Publishes the ENTIRE table, including unrelated pending fields/forms/views; pending contents are not locked/read completely. Referenced JS/images are NOT published by this request; use separate Web Resource publication. Compare changed button definitions after acceptance without running code or claiming UI/security/runtime success. Preserve published=true on readback failure; no reimport or automatic republish.

Input Schema

NameRequiredDescriptionDefault
dryRunNoDefault true. Read-only ExportSolution POST can occur during preflight; import/publish is not sent.
changesNo
dry_runNoDefault true. Read-only ExportSolution POST can occur during preflight; import/publish is not sent.
logicalNameNo
expectedHashNo
logical_nameNo
expected_hashNo
importReceiptNoUnchanged importReceipt from import_ribbon_solution in this server process. Cannot survive process restart; do not reimport to regenerate.
import_receiptNoUnchanged importReceipt from import_ribbon_solution in this server process. Cannot survive process restart; do not reimport to regenerate.
sourceFilePathNoAbsolute original unmanaged source ZIP path.
source_file_pathNoAbsolute original unmanaged source ZIP path.
candidateFilePathNoAbsolute candidate ZIP path produced from this source and the same structured edits on this server version.
candidate_file_pathNoAbsolute candidate ZIP path produced from this source and the same structured edits on this server version.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
allowFullTablePublishNoExplicitly accept publication of all other pending table customizations.
allowUnprotectedWriteNoExplicitly accept the remaining platform concurrency window; no atomic package/table/pending-customization lock.
allow_unprotected_writeNoExplicitly accept the remaining platform concurrency window; no atomic package/table/pending-customization lock.
allow_full_table_publishNoExplicitly accept publication of all other pending table customizations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.2
    • addedInput schema / properties / environment_profile
      Added value: +{
      +  "description": "Optional named environment profile for this call; omit to use the configured default.",
      +  "pattern": "^[A-Za-z][A-Za-z0-9_]{0,31}$",
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

B3.3/5.0
Behavior4/5

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

Goes well beyond the destructiveHint=true/readOnlyHint=false annotations: it warns the publish covers the ENTIRE table including unrelated pending fields/forms/views, that pending contents are not locked or fully read, and that there is a residual platform concurrency window. It also documents failure semantics (preserve published=true on readback failure, no reimport or automatic republish), which is exactly the kind of context annotations can't carry. Only the return/response behavior is left unstated.

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

Conciseness2/5

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

Seven dense sentences of jargon ("same-process authenticated import receipt", "successful bounded manifest log", "exportable non-Ribbon baseline") with no lead sentence stating purpose — the most important information is buried in the middle. Every sentence carries some content, but the ordering and compression make the definition hard to parse on first read.

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?

For a destructive 18-parameter mutation with no output schema, the description covers preconditions, blast radius, concurrency caveats and failure handling reasonably well. What is missing is a clear statement of the tool's outcome and what the caller gets back after a successful publish, plus the acceptance/verification step is described only as a caution rather than a procedure.

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 72%, so the schema already explains dry_run, import_receipt, source/candidate paths and the two allow_* flags. The description names planHash, allow_unprotected_write and allow_full_table_publish, but only restates what the schema says rather than adding format or validation meaning. Baseline 3 is appropriate given the schema does most of the work.

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

Purpose3/5

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

The tool's core action is never stated plainly in a single verb+resource sentence; the opening line ("Separate preview/publish after a same-process authenticated import receipt, matching native succeeded import job and successful bounded manifest log") is a dense precondition clause rather than a statement of what the tool does. "Publishes the ENTIRE table" and "before native PublishXml" imply a ribbon/table publish, but an agent must already know the domain to infer it. Sibling differentiation only appears obliquely via references to Web Resource publication.

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?

Prerequisites are explicit: a same-process, authenticated import receipt is required and cannot be regenerated by reimporting. It also states an exclusion and alternative — referenced JS/images are NOT published by this request and require separate Web Resource publication — which maps directly to the publish_web_resource sibling. It does not contrast with publish_appmodule or publish_model_table, so it falls short of a full when/when-not matrix.

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