assets-delete

To delete Unity assets by path, you provide the specific file paths to the removal tool, which then safely removes them from the project and automatically runs AssetDatabase.Refresh() to update the asset database.

The safest way to remove unused Unity assets is using an automated path-based deletion tool that validates input paths and reports failures without partial deletions, preventing project damage during migration or build cleanup.

Yes, you can automate pruning obsolete Unity models and textures by specifying their file paths in a batch deletion command, which removes the assets and refreshes the AssetDatabase to reflect changes.

AssetDatabase.Refresh runs automatically after asset deletions to synchronize the Unity project's internal database with the file system, ensuring the editor immediately recognizes removed files and reports any encountered errors.

If a Unity asset deletion fails due to an invalid path, the operation reports the error and prevents partial deletions, ensuring the project remains stable and undamaged without inconsistent asset states.

Yes, automated asset deletion works within Unity MCP workflows by accepting path arrays to remove specified assets, making it suitable for maintenance tasks like pruning unused files and cleaning up builds via automation.