Skip to main content
Glama
delano
by delano

delete_collection_request

Deletes a specific request from a Postman collection using collection and request IDs.

Instructions

Delete a request from a collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesCollection ID
request_idYesRequest ID

Implementation Reference

  • The main handler method that executes the delete_collection_request tool logic. It makes an HTTP DELETE request to /collections/{collection_id}/requests/{request_id} via the Postman API client.
    /**
     * Delete a request from a collection
     */
    async deleteCollectionRequest(args: any): Promise<ToolCallResponse> {
      const response = await this.client.delete(
        `/collections/${args.collection_id}/requests/${args.request_id}`
      );
      return this.createResponse(response.data);
    }
  • TypeScript interface defining the input schema for DeleteCollectionRequest. Extends CollectionIdArg (which provides collection_id) and adds request_id.
    export interface DeleteCollectionRequestArgs extends CollectionIdArg {
      request_id: string;
    }
  • Tool definition registration with input schema that declares collection_id and request_id as required string properties.
    {
      name: 'delete_collection_request',
      description: 'Delete a request from a collection',
      inputSchema: {
        type: 'object',
        properties: {
          collection_id: {
            type: 'string',
            description: 'Collection ID',
          },
          request_id: {
            type: 'string',
            description: 'Request ID',
          },
        },
        required: ['collection_id', 'request_id'],
      },
    },
  • Routes the 'delete_collection_request' tool name to the deleteCollectionRequest handler method via a switch statement in handleToolCall.
    case 'delete_collection_request':
      return await this.deleteCollectionRequest(args);
  • CollectionIdArg base interface providing collection_id field, which is extended by DeleteCollectionRequestArgs.
    export interface CollectionIdArg {
      collection_id: string;
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without disclosing effects like irreversibility, permission needs, or cascading deletions.

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?

Single sentence is concise and front-loaded, but could be slightly more informative without losing brevity.

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?

For a simple delete tool with two required parameters and no output schema, the description is minimally adequate but lacks error conditions or behavioral notes.

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 parameters are fully described; the description adds no extra meaning beyond what the schema already provides.

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 uses a specific verb ('Delete') and resource ('request from a collection'), clearly distinguishing it from sibling tools like create_collection_request or update_collection_request.

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, nor are there any prerequisites or exclusions mentioned.

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