Skip to main content
Glama

addCidToPaymentInstruction

Associates a CID with a payment instruction to enable x402 monetization for IPFS content on Pinata MCP server.

Instructions

Associate a CID with a payment instruction for x402 monetization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe payment instruction ID
cidYesThe CID to associate

Implementation Reference

  • The complete implementation of the addCidToPaymentInstruction tool, including its registration with the MCP server and the handler function that makes a PUT request to the Pinata API to associate a CID with a payment instruction.
    server.tool(
      "addCidToPaymentInstruction",
      "Associate a CID with a payment instruction for x402 monetization",
      {
        id: z.string().describe("The payment instruction ID"),
        cid: z.string().describe("The CID to associate"),
      },
      async ({ id, cid }) => {
        try {
          const url = `https://api.pinata.cloud/v3/x402/payment_instructions/${id}/cids/${cid}`;
    
          const response = await fetch(url, {
            method: "PUT",
            headers: getHeaders(),
          });
    
          if (!response.ok) {
            throw new Error(
              `Failed to add CID to payment instruction: ${response.status} ${response.statusText}`
            );
          }
    
          const data = await response.json();
          return {
            content: [
              {
                type: "text",
                text: `✅ CID added to 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 the full burden of behavioral disclosure. It implies a mutation ('Associate') but doesn't specify permissions required, whether the association is reversible, error conditions, or side effects. This is inadequate for a tool that modifies data without structured safety hints.

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 with zero waste. It is front-loaded with the core action and purpose, making it easy to parse quickly 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 as a mutation with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, error handling, or return values, which are critical for safe and effective use in an automated context.

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 ('id' and 'cid') fully. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, resulting in a baseline score of 3.

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 ('Associate') and the resources involved ('a CID with a payment instruction'), specifying the purpose for 'x402 monetization'. It distinguishes from sibling tools like 'removeCidFromPaymentInstruction' by indicating an addition rather than removal, though it doesn't explicitly compare to other CID-related tools.

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 payment instruction), exclusions, or comparisons to sibling tools like 'listPaymentInstructionCids' or 'createPaymentInstruction', leaving usage context unclear.

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