Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_publish_web_resources

Publish web resources to make them available in Microsoft Dynamics CRM and Power Platform systems for deployment and management.

Instructions

Publica web resources para torná-los disponíveis no sistema

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
webResourceIdsYesIDs dos web resources a publicar

Implementation Reference

  • The handler for `dynamics_publish_web_resources` that executes the PublishXml action via the Dataverse client.
    // 4. Publish Web Resources
    server.tool(
      "dynamics_publish_web_resources",
      "Publica web resources para torná-los disponíveis no sistema",
      PublishWebResourceSchema.shape,
      async (params: z.infer<typeof PublishWebResourceSchema>) => {
        const parameterXml = `<importexportxml><webresources>${params.webResourceIds.map((id) => `<webresource>{${id}}</webresource>`).join("")}</webresources></importexportxml>`;
    
        await client.executeAction("PublishXml", {
          ParameterXml: parameterXml,
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: `${params.webResourceIds.length} web resource(s) publicado(s) com sucesso!`,
            },
          ],
        };
      }
    );
  • Input validation schema for `dynamics_publish_web_resources`.
    export const PublishWebResourceSchema = z.object({
      webResourceIds: z.array(z.string()).describe("IDs dos web resources a publicar"),
    });
  • Tool registration for `dynamics_publish_web_resources`.
    server.tool(
      "dynamics_publish_web_resources",
      "Publica web resources para torná-los disponíveis no sistema",
      PublishWebResourceSchema.shape,
      async (params: z.infer<typeof PublishWebResourceSchema>) => {
        const parameterXml = `<importexportxml><webresources>${params.webResourceIds.map((id) => `<webresource>{${id}}</webresource>`).join("")}</webresources></importexportxml>`;
    
        await client.executeAction("PublishXml", {
          ParameterXml: parameterXml,
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: `${params.webResourceIds.length} web resource(s) publicado(s) com sucesso!`,
            },
          ],
        };
      }
    );
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 lacks behavioral details. It mentions making resources 'disponíveis no sistema' (available in the system), which implies a deployment or activation action, but doesn't specify if this is destructive, requires permissions, has side effects, or involves rate limits. More context on the publish operation's impact is needed.

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?

The description is a single, efficient sentence in Portuguese that directly states the tool's purpose. It's front-loaded with the key action and resource, with no wasted words. However, it could be slightly more structured by including usage context.

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?

For a tool that performs a publish operation (likely a mutation) with no annotations and no output schema, the description is incomplete. It doesn't explain what 'publica' entails (e.g., deployment, activation), potential outcomes, error conditions, or system impacts. More detail is needed given the complexity implied by the action.

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 100%, with the parameter 'webResourceIds' clearly documented as IDs of web resources to publish. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate given the schema does the heavy lifting.

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 the action ('Publica' meaning 'Publish') and the resource ('web resources'), making the purpose understandable. It distinguishes from siblings like 'dynamics_create_web_resource' (creation) and 'dynamics_delete_web_resource' (deletion), but doesn't explicitly differentiate from 'dynamics_publish_customizations' which might have overlapping functionality.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing existing web resources), exclusions, or compare it to similar tools like 'dynamics_publish_customizations'. The description only states what it does, not when it should be used.

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