Skip to main content
Glama
runpod

RunPod MCP Server

Official
by runpod

delete-network-volume

Delete a RunPod network volume by providing its ID to free up resources and clean up unused storage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkVolumeIdYesID of the network volume to delete

Implementation Reference

  • The handler function for the 'delete-network-volume' tool. It sends a DELETE request to /networkvolumes/{networkVolumeId} using the runpodRequest helper.
    // Delete Network Volume
    server.tool(
      'delete-network-volume',
      {
        networkVolumeId: z.string().describe('ID of the network volume to delete'),
      },
      async (params) => {
        const result = await runpodRequest(
          `/networkvolumes/${params.networkVolumeId}`,
          'DELETE'
        );
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      }
    );
  • Input schema: requires 'networkVolumeId' as a string, validated with Zod.
    {
      networkVolumeId: z.string().describe('ID of the network volume to delete'),
    },
  • src/index.ts:1320-1340 (registration)
    Registration of the 'delete-network-volume' tool via server.tool() on the MCP server instance.
    server.tool(
      'delete-network-volume',
      {
        networkVolumeId: z.string().describe('ID of the network volume to delete'),
      },
      async (params) => {
        const result = await runpodRequest(
          `/networkvolumes/${params.networkVolumeId}`,
          'DELETE'
        );
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      }
    );
  • The runpodRequest helper function that makes authenticated HTTP requests to the RunPod API.
    async function runpodRequest(
      endpoint: string,
      method: string = 'GET',
      body?: Record<string, unknown>
    ) {
      const url = `${API_BASE_URL}${endpoint}`;
      const headers = {
        Authorization: `Bearer ${API_KEY}`,
        'Content-Type': 'application/json',
      };
    
      const options: NodeFetchRequestInit = {
        method,
        headers,
      };
    
      if (body && (method === 'POST' || method === 'PATCH')) {
        options.body = JSON.stringify(body);
      }
    
      try {
        const response = await fetch(url, options);
    
        if (!response.ok) {
          const errorText = await response.text();
          throw new Error(`RunPod API Error: ${response.status} - ${errorText}`);
        }
    
        // Some endpoints might not return JSON
        const contentType = response.headers.get('content-type');
        if (contentType && contentType.includes('application/json')) {
          return await response.json();
        }
    
        return { success: true, status: response.status };
      } catch (error) {
        console.error('Error calling RunPod API:', error);
        throw error;
      }
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/runpod/runpod-mcp-ts'

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