Skip to main content
Glama

updateGroup

Modify metadata for existing Pinata groups to update names or network settings using the group's unique ID.

Instructions

Update metadata for an existing group on Pinata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNoWhether the group is in public or private IPFSpublic
idYesThe unique ID of the group to update
nameNoNew name for the group

Implementation Reference

  • Input schema for updateGroup tool - defines network, id, and optional name parameters using zod validation
    {
      network: z
        .enum(["public", "private"])
        .default("public")
        .describe("Whether the group is in public or private IPFS"),
      id: z.string().describe("The unique ID of the group to update"),
      name: z.string().optional().describe("New name for the group"),
    },
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 an update operation, implying mutation, but doesn't cover critical aspects like required permissions, whether changes are reversible, rate limits, error conditions, or what happens to unspecified metadata fields. This leaves significant 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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every word contributing to understanding what the tool does.

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 insufficient. It doesn't explain what 'metadata' encompasses beyond the schema parameters, what the update response contains, error handling, or side effects. Given the complexity of updating resources and lack of structured safety information, more context is needed.

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 all parameters thoroughly. The description adds no additional parameter information beyond what's in the schema (e.g., it doesn't clarify 'metadata' scope or provide examples). This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('Update metadata') and resource ('an existing group on Pinata'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'updateFile' or 'updatePaymentInstruction' beyond the resource type, which prevents a perfect score.

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. It doesn't mention prerequisites (e.g., needing an existing group ID), contrast with similar tools like 'createGroup' or 'deleteGroup', or specify scenarios where this update is appropriate versus creating a new group.

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