Skip to main content
Glama

removeCidFromPaymentInstruction

Remove a CID association from a payment instruction in Pinata MCP to manage IPFS content links and update payment records.

Instructions

Remove a CID association from a payment instruction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe payment instruction ID
cidYesThe CID to remove

Implementation Reference

  • Complete implementation of the removeCidFromPaymentInstruction tool. It's registered with the MCP server, takes payment instruction ID and CID as parameters, and makes a DELETE request to the Pinata API to remove the CID association from the payment instruction.
    server.tool(
      "removeCidFromPaymentInstruction",
      "Remove a CID association from a payment instruction",
      {
        id: z.string().describe("The payment instruction ID"),
        cid: z.string().describe("The CID to remove"),
      },
      async ({ id, cid }) => {
        try {
          const url = `https://api.pinata.cloud/v3/x402/payment_instructions/${id}/cids/${cid}`;
    
          const response = await fetch(url, {
            method: "DELETE",
            headers: getHeaders(),
          });
    
          if (!response.ok) {
            throw new Error(
              `Failed to remove CID from payment instruction: ${response.status} ${response.statusText}`
            );
          }
    
          const data = await response.json();
          return {
            content: [
              {
                type: "text",
                text: `✅ CID removed from payment instruction 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 only states the action without disclosing behavioral traits like whether this is a destructive operation, permission requirements, side effects, or error conditions. It lacks context on what 'remove' entails beyond the basic meaning.

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, clear sentence with zero wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration.

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?

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is insufficient. It doesn't cover what happens after removal, potential errors, or confirmation of success, leaving significant gaps for an AI agent to understand the tool's full behavior.

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 fully documents both parameters ('id' and 'cid'). The description adds no additional meaning beyond implying these parameters are used for the removal, which aligns with the schema but doesn't enhance understanding. Baseline 3 is appropriate here.

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 target ('a CID association from a payment instruction'), which is specific and unambiguous. However, it doesn't explicitly differentiate from its sibling 'removeFileFromGroup' or other removal operations, keeping it from 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?

No guidance is provided on when to use this tool versus alternatives like 'deletePaymentInstruction' or 'updatePaymentInstruction', nor does it mention prerequisites such as needing an existing CID association. The description only states what it does, not when or why to use it.

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