Skip to main content
Glama

deleteFileVectors

Remove vector data associated with a specific file to manage storage and optimize search performance in the Pinata MCP server.

Instructions

Delete vectors for a file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_idYesID of the file to delete vectors for

Implementation Reference

  • The deleteFileVectors tool handler - deletes vector embeddings for a file by making a DELETE request to the Pinata vectorize API endpoint. Takes a file_id parameter and returns a success message with the API response or an error.
    server.tool(
      "deleteFileVectors",
      "Delete vectors for a file",
      {
        file_id: z.string().describe("ID of the file to delete vectors for"),
      },
      async ({ file_id }) => {
        try {
          const url = `https://uploads.pinata.cloud/v3/vectorize/files/${file_id}`;
    
          const response = await fetch(url, {
            method: "DELETE",
            headers: getHeaders(),
          });
    
          if (!response.ok) {
            throw new Error(
              `Failed to delete file vectors: ${response.status} ${response.statusText}`
            );
          }
    
          const data = await response.json();
          return {
            content: [
              {
                type: "text",
                text: `✅ File vectors deleted\n\n${JSON.stringify(data, null, 2)}`,
              },
            ],
          };
        } catch (error) {
          return errorResponse(error);
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool deletes vectors, implying a destructive operation, but doesn't specify if this is reversible, requires specific permissions, affects file data, or has side effects like rate limits. This leaves significant gaps in understanding the tool's behavior.

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 extremely concise with a single sentence, 'Delete vectors for a file', which is front-loaded and wastes no words. It efficiently conveys the core action without unnecessary elaboration, making it easy to parse.

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 doesn't explain what 'vectors' are, the impact of deletion, error conditions, or return values. Given the complexity implied by sibling tools like 'vectorizeFile' and 'queryVectors', more context is needed to ensure safe and correct usage.

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?

The input schema has 100% description coverage, with the single parameter 'file_id' clearly documented. The description adds no additional meaning beyond the schema, such as explaining what 'vectors' are or how the deletion process works. Given the high schema coverage, a baseline score of 3 is appropriate.

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 'Delete vectors for a file' clearly states the action (delete) and target (vectors for a file), making the purpose understandable. However, it lacks differentiation from sibling tools like 'deleteFile' or 'vectorizeFile', which would require specifying what 'vectors' refer to in this context (e.g., embeddings, metadata).

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. For instance, it doesn't clarify if this should be used after 'vectorizeFile' or instead of 'deleteFile', nor does it mention prerequisites like needing an existing file with vectors. The description offers only basic usage without context.

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/PinataCloud/pinata-mcp'

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