Skip to main content
Glama
playcanvas

PlayCanvas Editor MCP Server

Official
by playcanvas

delete_assets

Remove one or more assets from the PlayCanvas Editor by specifying their IDs. This tool helps manage and clean up resources in real-time 3D web applications efficiently.

Instructions

Delete one or more assets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesThe asset IDs of the assets to delete

Implementation Reference

  • Registration of the MCP 'delete_assets' tool, including input schema and handler function that delegates to WSS.
    mcp.tool(
        'delete_assets',
        'Delete one or more assets',
        {
            ids: z.array(AssetIdSchema).nonempty().describe('The asset IDs of the assets to delete')
        },
        ({ ids }) => {
            return wss.call('assets:delete', ids);
        }
    );
  • AssetIdSchema: Zod schema for asset ID (number, nullable), used in delete_assets input.
    export const AssetIdSchema = z.number().int().nullable().describe('An asset ID.');
  • Handler function for delete_assets tool, calls WSS to perform the deletion.
    ({ ids }) => {
        return wss.call('assets:delete', ids);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Delete' implies a destructive mutation, but the description doesn't disclose whether deletion is permanent, requires specific permissions, affects related data, or has rate limits. For a destructive tool with zero annotation coverage, this is a significant gap in behavioral context.

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 with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place by specifying the verb, resource, and scope.

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 destructive tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after deletion (e.g., confirmation, error handling, or effects on related entities), nor does it cover permissions or safety considerations. Given the complexity and risk of deletion, more context is needed.

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%, so the schema fully documents the 'ids' parameter as an array of asset IDs. The description adds no additional parameter semantics beyond implying deletion applies to multiple assets ('one or more'), which is already clear from the schema's array type and minItems constraint.

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 verb ('Delete') and resource ('assets'), specifying it can handle 'one or more' assets. It distinguishes from siblings like 'delete_entities' by specifying the resource type. However, it doesn't explicitly contrast with other deletion tools beyond naming the resource.

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 provides no guidance on when to use this tool versus alternatives like 'delete_entities' or other asset-related operations. It doesn't mention prerequisites, consequences, or typical use cases. The agent must infer usage from the tool name alone.

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

Related 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/playcanvas/editor-mcp-server'

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