Skip to main content
Glama

w3_can_upload_rm

Removes an upload listing by its root CID from the MCP IPFS server without deleting the associated blobs or shards, enabling advanced data management.

Instructions

Removes an upload listing by its root CID (advanced use). Does not remove the underlying blobs/shards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootCidYesRoot CID of the upload to remove from the list.

Implementation Reference

  • The handler function that executes the tool logic: parses args with W3CanUploadRmArgsSchema, runs 'can upload rm {rootCid}' command, returns formatted response with stdout.
    const handleW3CanUploadRm: ToolHandler = async (args) => {
      const parsed = Schemas.W3CanUploadRmArgsSchema.safeParse(args);
      if (!parsed.success)
        throw new Error(
          `Invalid arguments for w3_can_upload_rm: ${parsed.error.message}`
        );
      const { rootCid } = parsed.data;
      const { stdout } = await runW3Command(`can upload rm ${rootCid}`);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              message: `Upload ${rootCid} removed successfully.`,
              output: stdout.trim(),
            }),
          },
        ],
      };
    };
  • Zod schema defining the input arguments for the w3_can_upload_rm tool: requires rootCid string.
    export const W3CanUploadRmArgsSchema = z
      .object({
        rootCid: z
          .string()
          .describe("Root CID of the upload to remove from the list."),
      })
      .describe(
        "Removes an upload listing by its root CID (advanced use). Does not remove the underlying blobs/shards."
      );
  • Registration of the tool handler in the toolHandlers map.
    w3_can_upload_rm: handleW3CanUploadRm,
Behavior3/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 clearly states the tool's action ('Removes an upload listing') and a key limitation ('Does not remove the underlying blobs/shards'), which is valuable context. However, it lacks details on permissions, side effects, error handling, or response format, leaving behavioral aspects partially uncovered 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 two concise sentences that are front-loaded with the core action and efficiently convey essential information: the operation, target, usage context, and limitation. Every sentence earns its place with no wasted words, making it highly efficient and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 partially complete. It covers the purpose and a key behavioral trait (non-destructive to blobs/shards), but lacks details on permissions, return values, error conditions, or integration with sibling tools, leaving gaps for an advanced-use mutation tool.

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%, with the parameter 'rootCid' fully documented in the schema as 'Root CID of the upload to remove from the list.' The description adds no additional parameter details beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Removes an upload listing') and the target resource ('by its root CID'), distinguishing it from sibling tools like w3_can_upload_ls (list) and w3_can_upload_add (add). It also specifies the scope ('advanced use') and what is not affected ('Does not remove the underlying blobs/shards'), making the purpose highly specific and well-differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context with 'advanced use', indicating this is for specialized scenarios rather than routine operations. However, it does not explicitly state when to use this tool versus alternatives like w3_rm or w3_can_blob_rm, nor does it mention prerequisites or exclusions, leaving some guidance gaps compared to explicit sibling differentiation.

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

Related 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/alexbakers/mcp-ipfs'

If you have feedback or need assistance with the MCP directory API, please join our Discord server