Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

create_web_resource_and_publish

Destructive

Creates a Dynamics 365 web resource with a non-overwriting name, then optionally publishes it; use dry_run to preview changes before saving.

Instructions

Create a Web Resource without overwriting an existing saved name. Defaults to scoped PublishXml after saving. publish=false saves only; dry_run=true previews without writing. A publication error preserves saved=true and the created ID; recover with publish_web_resource.

Input Schema

NameRequiredDescriptionDefault
nameYes
dryRunNoCompatibility alias for dry_run; conflicting aliases are rejected.
contentNoInline content, UTF-8 by default. Supply exactly one of content or file_path; empty content is allowed.
dry_runNoRead-only preview showing the environment, target, metadata changes and content hashes. Does not save or publish.
publishNoDefault true preserves the old save-and-publish behavior. Set false to save without publishing.
filePathNoCompatibility alias for file_path; conflicting aliases are rejected.
file_pathNoAbsolute source-file path on the MCP server machine; read as bytes and Base64 encoded. Supply exactly one of file_path or content. Maximum 10 MiB.
descriptionNoOptional description; an empty string clears it.
displayNameNoCompatibility alias for display_name; conflicting aliases are rejected.
display_nameNo
contentEncodingNoCompatibility alias for content_encoding; conflicting aliases are rejected.
webResourceTypeNoCompatibility alias for web_resource_type; conflicting aliases are rejected.
content_encodingNoInline content encoding, default utf8. Base64 must be canonical. Not used with file_path.
web_resource_typeNo1 HTML, 2 CSS, 3 JS, 4 XML, 5 PNG, 6 JPG, 7 GIF, 8 XAP, 9 XSL, 10 ICO, 11 SVG, 12 RESX; platform/version support is validated on save.
solutionUniqueNameNoCompatibility alias for solution_unique_name; conflicting aliases are rejected.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
solution_unique_nameNoOptional unmanaged solution unique name, sent in MSCRM.SolutionUniqueName when creating.

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.1/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it confirms creation does not overwrite an existing saved name, discloses the default PublishXml side effect, explains dry-run behavior, and describes partial-failure semantics where saved=true and the created ID are preserved. Recovery via publish_web_resource is also stated.

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?

The description is front-loaded and tightly structured. Each sentence adds practical information: no-overwrite behavior, default publish semantics, flag alternatives, and failure recovery.

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 17-parameter mutation tool with no output schema, the description covers the most important non-obvious behaviors: overwrite safety, default publishing, dry-run, and failure recovery. The rich input schema carries the remaining parameter detail, though some workflow-relevant parameter interactions are not described.

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 high at 88%, so the schema already documents most parameters. The description adds useful meaning around publish and dry_run behavior, but it does not clarify key parameters such as content versus file_path, aliases, encoding, solution association, or web_resource_type.

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

Purpose4/5

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

The description clearly states a specific verb and resource: create a Web Resource. It also notes the no-overwrite constraint and default publish behavior, which helps distinguish it from update-style siblings, though it does not explicitly name the sibling to use instead.

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?

It gives clear usage guidance for the main flags: default publish, publish=false for save-only, and dry_run=true for preview. It also names publish_web_resource as the recovery path after a publication error, but it does not explicitly explain when to create versus update an existing resource.

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