Skip to main content
Glama

getFileById

Retrieve detailed information about a specific file stored on Pinata's IPFS network using its unique identifier. Access file metadata and content from public or private IPFS storage.

Instructions

Retrieve detailed information about a specific file stored on Pinata by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNoWhether the file is in public or private IPFSpublic
idYesThe unique ID of the file to retrieve

Implementation Reference

  • The getFileById tool handler that retrieves detailed information about a specific file stored on Pinata by its ID. It takes network (public/private) and id parameters, makes a GET request to the Pinata API endpoint, and returns the response data.
    server.tool(
      "getFileById",
      "Retrieve detailed information about a specific file stored on Pinata by its ID",
      {
        network: z
          .enum(["public", "private"])
          .default("public")
          .describe("Whether the file is in public or private IPFS"),
        id: z.string().describe("The unique ID of the file to retrieve"),
      },
      async ({ network, id }) => {
        try {
          const url = `https://api.pinata.cloud/v3/files/${network}/${id}`;
    
          const response = await fetch(url, {
            method: "GET",
            headers: getHeaders(),
          });
    
          if (!response.ok) {
            throw new Error(
              `Failed to get file: ${response.status} ${response.statusText}`
            );
          }
    
          const data = await response.json();
          return successResponse(data);
        } catch (error) {
          return errorResponse(error);
        }
      }
    );
  • The input schema for getFileById tool using Zod validation. Defines two parameters: network (enum: public/private, defaults to public) and id (required string).
    {
      network: z
        .enum(["public", "private"])
        .default("public")
        .describe("Whether the file is in public or private IPFS"),
      id: z.string().describe("The unique ID of the file to retrieve"),
    },
  • The getHeaders helper function that returns authorization headers with the PINATA_JWT bearer token, used by the getFileById tool for API requests.
    const getHeaders = () => {
      if (!PINATA_JWT) {
        throw new Error("PINATA_JWT environment variable is not set");
      }
      return {
        Authorization: `Bearer ${PINATA_JWT}`,
        "Content-Type": "application/json",
      };
    };
  • Helper functions for consistent API responses - errorResponse for errors and successResponse for successful data returns, used by getFileById.
    const errorResponse = (error: unknown) => ({
      content: [
        {
          type: "text" as const,
          text: `Error: ${error instanceof Error ? error.message : String(error)}`,
        },
      ],
      isError: true,
    });
    
    // Helper for consistent success responses
    const successResponse = (data: unknown) => ({
      content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }],
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation but doesn't mention authentication requirements, rate limits, error behavior, or what 'detailed information' includes. For a read operation in a system with authentication tools like 'testAuthentication', this is insufficient.

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 immediately conveys the core purpose without any wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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 tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'detailed information' includes, authentication requirements, or error handling. Given the sibling tools include authentication and various file operations, more context is needed for proper agent 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?

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds no additional parameter context beyond what's in the schema descriptions. The baseline of 3 is appropriate when the schema does all the work.

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 ('Retrieve detailed information') and resource ('specific file stored on Pinata by its ID'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'searchFiles' or 'fetchFromGateway', but the specificity of 'by its ID' provides some implicit distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'searchFiles' or 'fetchFromGateway'. It doesn't mention prerequisites, error conditions, or typical use cases, leaving the agent to infer usage from the tool name and parameters alone.

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