Skip to main content
Glama

unreal_delete_blueprint

Deletes a Blueprint asset from an Unreal Engine 5 project, removing the selected Blueprint when it is no longer needed.

Instructions

Delete a Blueprint asset.

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": {
      "params": "<params>"
    },
    "name": "unreal_delete_blueprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: not whether deletion is permanent or how to recover, not what happens to references/instances of the blueprint, nor whether it operates on a path, a loaded asset, or an open editor buffer. For a destructive mutation, this is a severe disclosure gap.

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

Conciseness3/5

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

A single front-loaded sentence with zero filler, so nothing is wasted. However, the brevity is achieved by omission rather than by tight writing, leaving the definition under-specified for the operation it performs.

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?

An output schema exists, so return values need not be explained, but the tool is destructive with no annotations and an opaque "params" object. Given that complexity, the definition omits the safety, scope, and argument information an agent needs to invoke it correctly.

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 tool has one required parameter, "params", whose schema carries no description coverage at all — a 0% coverage gap the description does nothing to fill. It never says what "params" holds (asset path? name? object reference?), so the agent must guess the argument shape.

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 pairs a specific verb with a specific resource ("Delete a Blueprint asset"), so the operation is unambiguous and distinguishable by name from siblings like unreal_delete_blueprint_node and unreal_delete_asset. It stops short of explicitly differentiating itself from those lookalike siblings (e.g. asset vs. blueprint-asset vs. node deletion).

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?

There is no when-to-use guidance, no prerequisites, and no pointer to any alternative tool. An agent gets no help deciding between this and unreal_delete_asset or unreal_delete_blueprint_node when an asset is both a blueprint and a plain asset.

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