Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_list_web_resources

List and filter web resources in Microsoft Dynamics CRM by name, type, or solution to manage HTML, CSS, JavaScript, and other files for development workflows.

Instructions

Lista web resources com filtros opcionais

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameFilterNoFiltro por nome (contains)
typeNoTipo do web resource
solutionIdNoFiltrar por solução
topNo

Implementation Reference

  • The handler implementation for the dynamics_list_web_resources tool, which filters and fetches web resources from the Dynamics CRM API.
    server.tool(
      "dynamics_list_web_resources",
      "Lista web resources com filtros opcionais",
      ListWebResourcesSchema.shape,
      async (params: z.infer<typeof ListWebResourcesSchema>) => {
        const filters: string[] = ["ismanaged eq false"];
        if (params.nameFilter) {
          filters.push(`contains(name,'${params.nameFilter}')`);
        }
        if (params.type) {
          filters.push(`webresourcetype eq ${TYPE_MAP[params.type]}`);
        }
    
        const result = await client.list("webresourceset", {
          select: ["webresourceid", "name", "displayname", "webresourcetype", "description", "createdon", "modifiedon"],
          filter: filters.join(" and "),
          orderby: "name asc",
          top: params.top,
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Web resources encontrados: ${result.value.length}\n\n${JSON.stringify(result.value, null, 2)}`,
            },
          ],
        };
      }
    );
  • The schema definition (Zod) for the dynamics_list_web_resources tool input.
    export const ListWebResourcesSchema = z.object({
      nameFilter: z.string().optional().describe("Filtro por nome (contains)"),
      type: WebResourceTypeEnum.optional(),
      solutionId: z.string().optional().describe("Filtrar por solução"),
      top: z.number().default(50),
    });
  • The registration point of the dynamics_list_web_resources tool within the registerWebResourceTools function.
    "dynamics_list_web_resources",
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states it's a list operation with optional filters, implying read-only behavior, but doesn't disclose pagination (the 'top' parameter suggests it), rate limits, authentication requirements, or what happens if no filters are applied (e.g., returns all web resources). The description lacks details on output format, error conditions, or side effects.

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 a single, efficient sentence in Portuguese with zero waste—it directly states the tool's purpose and key feature (optional filters). It's appropriately sized for a list operation and front-loaded with essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (a list tool with 4 parameters, no annotations, and no output schema), the description is incomplete. It doesn't cover behavioral aspects like pagination, response format, or error handling, which are critical for an AI agent to use the tool correctly. The lack of annotations and output schema increases the burden on the description, which it doesn't meet.

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 75% (three parameters have descriptions, one 'top' has only a default), so the baseline is 3. The description adds little beyond the schema—it mentions 'filtros opcionais' (optional filters), which aligns with the schema's optional parameters, but doesn't explain filter logic (e.g., 'nameFilter' uses 'contains') or parameter interactions. No additional syntax or format details are provided.

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 'Lista web resources com filtros opcionais' clearly states the action (list) and resource (web resources) in Portuguese. It distinguishes from siblings like dynamics_get_web_resource_content (which retrieves content) and dynamics_create/update/delete_web_resource (which modify resources). However, it doesn't specify the scope (e.g., all web resources in the system) or explicitly differentiate from other list tools like dynamics_list_solutions.

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

Usage Guidelines2/5

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

The description mentions 'filtros opcionais' (optional filters), implying when to use parameters, but provides no guidance on when to choose this tool over alternatives. For example, it doesn't specify whether this is the primary listing tool for web resources or when to use it versus dynamics_list_solution_components (which might include web resources). No prerequisites or exclusions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rafteles2016/mcpDynamics'

If you have feedback or need assistance with the MCP directory API, please join our Discord server