Dataverse Plugin MCP

Overview Schema Source Related Servers Discussions Admin

delete_image

Remove a pre/post image from a Dataverse plug-in step while preserving the step itself. Use when an image is no longer needed.

Instructions

Delete a pre/post image from a step, without deleting the step itself.

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": {
      "image_id": "<image_id>"
    },
    "name": "delete_image"
  }
}

Input Schema

Name	Required	Description	Default
`image_id`	Yes
`environment`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It clarifies the scope (pre/post image, not the step) but does not mention whether the deletion is permanent, any required permissions, potential side effects, or reversibility. For a delete operation, this leaves significant gaps.

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, front-loaded sentence that states the core action and scope without extraneous words. It is appropriately sized for the tool's complexity, focusing on the key differentiator (not deleting the step).

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 lack of annotations, incomplete parameter explanations, and presence of sibling tools, the description does not provide enough context for an agent to select and invoke the tool confidently. It clarifies the tool's scope but omits usage guidelines, parameter semantics, and safety/behavioral details, making it inadequate for effective autonomous invocation.

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

Parameters1/5

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

The schema has 0% description coverage (only titles and types). The description does not explain the meaning or usage of image_id or environment parameters, nor how they relate to the 'pre/post image' concept. It adds no value beyond the parameter names themselves.

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?

The description clearly states the tool deletes a 'pre/post image from a step' and explicitly distinguishes it from deleting the step itself ('without deleting the step itself'). This specific verb+resource+scope makes it distinct from sibling tools like delete_step and update_image.

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

Usage Guidelines3/5

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

The description implies usage context—use this when you need to remove an image attached to a step rather than the step itself—but it does not explicitly state when to use it over alternatives or provide any exclusions. The distinction from deleting the step is helpful but not framed as formal guidance.

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