Skip to main content
Glama

removeFileFromGroup

Remove a specific file from a designated group in your Pinata IPFS storage to manage content organization and access control.

Instructions

Remove a file from a group in your Pinata account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNoWhether the group and file are in public or private IPFSpublic
groupIdYesThe ID of the group to remove the file from
fileIdYesThe ID of the file to remove from the group

Implementation Reference

  • Complete implementation of removeFileFromGroup tool - removes a file from a Pinata group via DELETE request to API endpoint
    server.tool(
      "removeFileFromGroup",
      "Remove a file from a group in your Pinata account",
      {
        network: z
          .enum(["public", "private"])
          .default("public")
          .describe("Whether the group and file are in public or private IPFS"),
        groupId: z
          .string()
          .describe("The ID of the group to remove the file from"),
        fileId: z.string().describe("The ID of the file to remove from the group"),
      },
      async ({ network, groupId, fileId }) => {
        try {
          const url = `https://api.pinata.cloud/v3/groups/${network}/${groupId}/ids/${fileId}`;
    
          const response = await fetch(url, {
            method: "DELETE",
            headers: getHeaders(),
          });
    
          if (!response.ok) {
            throw new Error(
              `Failed to remove file from group: ${response.status} ${response.statusText}`
            );
          }
    
          const data = await response.json();
          return {
            content: [
              {
                type: "text",
                text: `✅ File removed from group successfully\n\n${JSON.stringify(data, null, 2)}`,
              },
            ],
          };
        } catch (error) {
          return errorResponse(error);
        }
      }
    );
  • The removeFileFromGroup tool registration and handler implementation. Removes a file from a Pinata group by making a DELETE request to the API endpoint with network, groupId, and fileId parameters. Returns success message or error response.
    server.tool(
      "removeFileFromGroup",
      "Remove a file from a group in your Pinata account",
      {
        network: z
          .enum(["public", "private"])
          .default("public")
          .describe("Whether the group and file are in public or private IPFS"),
        groupId: z
          .string()
          .describe("The ID of the group to remove the file from"),
        fileId: z.string().describe("The ID of the file to remove from the group"),
      },
      async ({ network, groupId, fileId }) => {
        try {
          const url = `https://api.pinata.cloud/v3/groups/${network}/${groupId}/ids/${fileId}`;
    
          const response = await fetch(url, {
            method: "DELETE",
            headers: getHeaders(),
          });
    
          if (!response.ok) {
            throw new Error(
              `Failed to remove file from group: ${response.status} ${response.statusText}`
            );
          }
    
          const data = await response.json();
          return {
            content: [
              {
                type: "text",
                text: `✅ File removed from group successfully\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 full burden but offers minimal behavioral insight. It implies a mutation ('Remove') but doesn't disclose permissions required, whether the operation is reversible, rate limits, or what happens to the file/group post-removal (e.g., if the file persists elsewhere). This leaves significant gaps for a tool that likely alters data.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and context, 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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain the outcome (e.g., success response, error cases), side effects, or dependencies, leaving the agent with insufficient context to use it safely and effectively.

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%, providing clear documentation for all parameters (network, groupId, fileId). The description adds no additional parameter semantics beyond what's in the schema, such as format examples or interdependencies. Baseline 3 is appropriate since the schema handles the heavy lifting.

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 action ('Remove') and the target ('a file from a group'), specifying the context ('in your Pinata account'). It distinguishes from obvious siblings like 'addFileToGroup' and 'deleteFile', but doesn't explicitly differentiate from all related tools like 'deleteGroup' or 'updateGroup'.

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 an existing group and file), exclusions, or comparisons with tools like 'deleteFile' (which might delete entirely) or 'updateGroup' (which might modify membership differently).

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