delete_asset
Remove an asset from the library using its UUID and workspace ID.
Instructions
Delete an asset from the library
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workspace_id | Yes | Workspace slug or UUID | |
| id | Yes | Asset UUID |
Remove an asset from the library using its UUID and workspace ID.
Delete an asset from the library
| Name | Required | Description | Default |
|---|---|---|---|
| workspace_id | Yes | Workspace slug or UUID | |
| id | Yes | Asset UUID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only states 'delete' without disclosing side effects, permissions needed, whether deletion is permanent or reversible, or any cascading behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no unnecessary words. Front-loaded and efficient for a straightforward delete operation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Missing output schema; description does not explain return behavior (e.g., success confirmation) or warn about irreversibility. Incomplete for a mutation tool with no annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers both parameters with descriptions; description adds no extra meaning beyond schema. Baseline 3 appropriate due to high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'delete an asset', specifying the action and resource. It distinguishes from sibling delete tools by targeting 'asset', but doesn't clarify workspace context beyond schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like delete_amplification_post or delete_product, nor warnings about irreversibility or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ejwhite7/olli-social-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server