Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

publish_web_resource

Destructive

Publishes a saved Web Resource through native PublishXml without re-saving or re-uploading content, for save-only workflows or recovery after publish failures.

Instructions

Publish a single saved Web Resource with native PublishXml, without saving/re-uploading content. Use for save-only workflows or recovery after a publish failure. Publishes the latest saved version at execution time.

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": {
      "id": "<id>"
    },
    "name": "publish_web_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
dryRunNoCompatibility alias for dry_run; conflicting aliases are rejected.
dry_runNoPreview environment and the single-resource publication scope without executing PublishXml.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

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

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=true, so the safety profile is covered. The description adds real value by clarifying that no content is saved or re-uploaded and that the version published is whatever is saved at execution time, which matters for a destructive publish. It does not explain blast radius, whether a republish of an already-published resource is a no-op, or what a failure leaves behind, which is the main remaining behavioral gap.

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?

Three tight sentences, with the core action and its defining constraint front-loaded before the use cases and the execution-time versioning caveat. No filler or restatement of the tool name.

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 a destructive single-resource publish with no output schema, the description covers purpose, when to use it, what it does not do, and which version gets published. Remaining gaps are secondary: no statement of required permissions or of what the caller gets back on success or failure.

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 75%, and the schema already documents dry_run, its dryRun alias, and environment_profile, including the alias-conflict rejection rule. The description contributes nothing parameter-specific beyond the general 'without saving' framing, so the schema is doing the heavy lifting and 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?

States a specific verb and resource ('Publish a single saved Web Resource') plus the underlying mechanism ('native PublishXml'), and explicitly rules out the save/re-upload behavior that sibling tools like create_web_resource_and_publish and update_web_resource_and_publish perform. An agent can distinguish this from those siblings without opening any schema.

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?

Gives concrete when-to-use conditions: 'save-only workflows' and 'recovery after a publish failure.' That is a clear context for selection. It stops short of naming the alternative publish-with-save tools as exclusions, so the routing guidance is strong but not fully explicit.

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