Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

search_web_resources_by_name

Read-only

Find Dynamics 365 web resources by a name substring with bounded OData results, defaulting to published definitions and optionally including unpublished versions or Base64 content.

Instructions

Find Web Resources by a substring of name, with bounded OData results. Defaults to published definitions; include_unpublished=true reads the latest saved definitions. Content is excluded by default. Supports the legacy camelCase parameters.

Input Schema

NameRequiredDescriptionDefault
topNo
nameKeywordNoCompatibility alias for name_keyword; conflicting aliases are rejected.
name_keywordNo
includeContentNoCompatibility alias for include_content; conflicting aliases are rejected.
include_contentNoReturn Base64 source content only when explicitly requested.
includeUnpublishedNoCompatibility alias for include_unpublished; conflicting aliases are rejected.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
include_unpublishedNoRead latest saved definitions, including unpublished resources, using RetrieveUnpublishedMultiple.

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

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the description's job is incremental. It does add real context beyond the annotations: the published-vs-latest resolution behavior, the content-excluded default, the alias tolerance, and that results are bounded. It says nothing about pagination beyond the cap, ordering, or permissions required to read unpublished definitions.

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

Conciseness4/5

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

Four short sentences, no filler, and the search scope is front-loaded before the optional-behavior clauses. The comma-spliced 'bounded OData results' phrasing is slightly compressed, but every sentence carries information an agent needs.

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 8-parameter read tool with no output schema, the description covers the query parameter, the two behavioral flags, and the alias compatibility that would otherwise trip an agent up. The missing piece is what a returned web resource looks like and how environment_profile interacts with the configured default.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 75% schema coverage the schema already documents most parameters, but the description adds meaning the schema does not: include_unpublished selects a different read path (latest saved definitions), include_content is off unless requested, top is described as a bound, and the legacy camelCase aliases are called out. Only environment_profile remains unaddressed anywhere.

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 opens with a specific verb and resource ('Find Web Resources by a substring of name') plus the result-bounding behavior, which is enough to separate it from the write-oriented siblings like create_web_resource_and_publish, update_web_resource_and_publish and publish_web_resource. It never names a sibling explicitly as an alternative, so it falls short of a 5.

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 states the default scope ('Defaults to published definitions') and the condition that changes it ('include_unpublished=true reads the latest saved definitions'), and flags that content is opt-in. It gives no explicit when-not guidance or comparison to the other search tools such as search_records_by_odata, which keeps it at 4.

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