Skip to main content
Glama

delete_blob

Remove a blob from Walrus decentralized storage by specifying its blob ID to manage storage space and data lifecycle.

Instructions

Delete a blob from Walrus storage

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blobIdYesThe blob ID to delete

Implementation Reference

  • The tool handler for 'delete_blob' which parses input arguments using DeleteBlobSchema and delegates to walrusClient.deleteBlob(blobId), returning the result as JSON text.
    case 'delete_blob': {
      const { blobId } = DeleteBlobSchema.parse(args);
      const result = await walrusClient.deleteBlob(blobId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Zod schema for validating the input parameters of the delete_blob tool (requires blobId string).
    const DeleteBlobSchema = z.object({
      blobId: z.string().describe('The blob ID to delete'),
    });
  • src/index.ts:102-115 (registration)
    Registration of the 'delete_blob' tool in the list_tools response, including name, description, and input schema.
    {
      name: 'delete_blob',
      description: 'Delete a blob from Walrus storage',
      inputSchema: {
        type: 'object',
        properties: {
          blobId: {
            type: 'string',
            description: 'The blob ID to delete',
          },
        },
        required: ['blobId'],
      },
    },
  • Implementation of deleteBlob method in WalrusClient class. Currently a stub that always returns failure since Walrus does not support manual blob deletion.
    async deleteBlob(blobId: string): Promise<{ success: boolean; message: string }> {
      // Note: Walrus blobs cannot be deleted once stored - they expire based on their epoch settings
      return {
        success: false,
        message: 'Walrus blobs cannot be manually deleted. They will expire automatically based on their storage epochs.',
      };
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if deletion is permanent, requires specific permissions, has rate limits, or what happens on success/failure, which is inadequate for a destructive operation.

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, direct sentence with zero waste, front-loading the core action. It's appropriately sized for a simple tool, making it easy to parse quickly.

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 incomplete. It lacks critical context like irreversible effects, error handling, or return values, leaving significant gaps in understanding the tool's behavior.

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 input schema fully documents the 'blobId' parameter. The description adds no additional meaning beyond implying the parameter is used for deletion, meeting the baseline for high schema coverage without extra value.

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 ('a blob from Walrus storage'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_blob' or 'store_blob' beyond the obvious action difference, missing explicit comparison.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing the blob ID), exclusions, or comparisons to siblings like 'list_blobs' for finding IDs, leaving usage context vague.

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

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/Motion-Labs-Sui/walrus-mcp'

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