Skip to main content
Glama
delano
by delano

delete_collection_folder

Delete a folder from a Postman collection by providing its collection and folder IDs.

Instructions

Delete a folder from a collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesCollection ID
folder_idYesFolder ID

Implementation Reference

  • The handler function that executes the delete_collection_folder logic. It calls this.client.delete() with the collection_id and folder_id from args, then returns the response wrapped via createResponse().
    async deleteCollectionFolder(args: any): Promise<ToolCallResponse> {
      const response = await this.client.delete(
        `/collections/${args.collection_id}/folders/${args.folder_id}`
      );
      return this.createResponse(response.data);
    }
  • The tool definition/schema for delete_collection_folder. Specifies the tool name, description, and inputSchema with required fields collection_id (string) and folder_id (string).
    {
      name: 'delete_collection_folder',
      description: 'Delete a folder from a collection',
      inputSchema: {
        type: 'object',
        properties: {
          collection_id: {
            type: 'string',
            description: 'Collection ID',
          },
          folder_id: {
            type: 'string',
            description: 'Folder ID',
          },
        },
        required: ['collection_id', 'folder_id'],
      },
    },
  • The switch-case registration that routes 'delete_collection_folder' to the deleteCollectionFolder handler method.
    case 'delete_collection_folder':
      return await this.deleteCollectionFolder(args);
  • The TypeScript interface DeleteCollectionFolderArgs that defines the typed arguments (extends CollectionIdArg with folder_id: string).
    export interface DeleteCollectionFolderArgs extends CollectionIdArg {
      folder_id: string;
    }
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavior, but it does not mention idempotency, return values, side effects, or permissions. This is inadequate for a delete operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise, one sentence with no wasted words. However, it may be too terse for a tool requiring context.

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?

The description lacks essential context such as error handling, prerequisites, or differentiation from similar endpoints. Given the tool's simplicity, more details are 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 coverage is 100%, so baseline 3. The description adds no extra meaning beyond the schema's parameter descriptions ('Collection ID', 'Folder ID').

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 action ('Delete') and the resource ('folder from a collection'), distinguishing it from sibling tools like create, update, or get collection folder.

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 on when to use this tool vs. alternatives, no prerequisites mentioned (e.g., folder existence, permissions), and no exclusions provided.

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/delano/postman-mcp-server'

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