Skip to main content
Glama

createGroup

Organize files in your Pinata account by creating a new group for public or private IPFS storage.

Instructions

Create a new group in your Pinata account to organize files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNoWhether to create the group in public or private IPFSpublic
nameYesName for the new group

Implementation Reference

  • The createGroup tool handler implementation that creates a new group in Pinata IPFS. It accepts network (public/private) and name parameters, makes a POST request to Pinata's v3/groups API, and returns the created group details or an error response.
    server.tool(
      "createGroup",
      "Create a new group in your Pinata account to organize files",
      {
        network: z
          .enum(["public", "private"])
          .default("public")
          .describe("Whether to create the group in public or private IPFS"),
        name: z.string().describe("Name for the new group"),
      },
      async ({ network, name }) => {
        try {
          const url = `https://api.pinata.cloud/v3/groups/${network}`;
    
          const response = await fetch(url, {
            method: "POST",
            headers: getHeaders(),
            body: JSON.stringify({ name }),
          });
    
          if (!response.ok) {
            throw new Error(
              `Failed to create group: ${response.status} ${response.statusText}`
            );
          }
    
          const data = await response.json();
          return {
            content: [
              {
                type: "text",
                text: `✅ Group created 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 for behavioral disclosure. While 'Create' implies a write operation, it doesn't specify authentication requirements, rate limits, whether groups are permanent or deletable, what happens on success/failure, or any side effects. This leaves significant behavioral gaps for a mutation tool.

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 communicates the core purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information, 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 insufficiently complete. It doesn't explain what a 'group' represents in Pinata's system, what capabilities groups provide, what happens after creation, or any constraints on group names. The context signals indicate this is a 2-parameter tool with significant behavioral implications that aren't addressed.

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?

With 100% schema description coverage, the schema already documents both parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline expectation but doesn't provide extra value regarding parameter meaning or usage.

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 ('Create a new group') and resource ('in your Pinata account to organize files'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this from sibling tools like 'listGroups' or 'updateGroup' beyond the basic verb 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 'updateGroup' or 'deleteGroup', nor does it mention prerequisites or context for group creation. It simply states what the tool does without indicating appropriate usage scenarios.

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