Skip to main content
Glama
delano
by delano

delete_collection_response

Delete a specific response from a Postman collection by providing the collection ID and response ID.

Instructions

Delete a response from a collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesCollection ID
response_idYesResponse ID

Implementation Reference

  • The async method `deleteCollectionResponse` that executes the tool logic by calling `this.client.delete()` on the API endpoint `/collections/{collection_id}/responses/{response_id}`.
    async deleteCollectionResponse(args: any): Promise<ToolCallResponse> {
      const response = await this.client.delete(
        `/collections/${args.collection_id}/responses/${args.response_id}`
      );
      return this.createResponse(response.data);
    }
  • The TypeScript interface `DeleteCollectionResponseArgs` extending `CollectionIdArg` with a required `response_id` string field.
    export interface DeleteCollectionResponseArgs extends CollectionIdArg {
      response_id: string;
    }
  • The tool definition/input schema for `delete_collection_response`, specifying `collection_id` and `response_id` as required string properties.
    {
      name: 'delete_collection_response',
      description: 'Delete a response from a collection',
      inputSchema: {
        type: 'object',
        properties: {
          collection_id: {
            type: 'string',
            description: 'Collection ID',
          },
          response_id: {
            type: 'string',
            description: 'Response ID',
          },
        },
        required: ['collection_id', 'response_id'],
      },
    },
  • The case statement in the tool routing switch that maps the tool name `'delete_collection_response'` to the handler method `this.deleteCollectionResponse(args)`.
    case 'delete_collection_response':
      return await this.deleteCollectionResponse(args);
Behavior2/5

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

Missing annotations; description only states the action without disclosing side effects, permanence, permissions, or error behavior.

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?

One short sentence, no waste. Could include more context without harming conciseness.

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?

Lacks details on return values, error handling, or confirmation of deletion. For a delete operation, more behavioral context is 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%; both parameters are documented in the schema. The description adds no additional parameter context, so baseline of 3 is appropriate.

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 (response from a collection), distinguishing it from siblings like delete_collection_request or delete_server_response.

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 versus alternatives, no prerequisites or contextual hints 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