Skip to main content
Glama
delano
by delano

get_collection_response

Get details of a specific response in a collection by providing collection and response IDs. Optionally populate full response contents.

Instructions

Get details of a specific response in a collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesCollection ID
response_idYesResponse ID
idsNoReturn only properties that contain ID values
uidNoReturn all IDs in UID format
populateNoReturn all response contents

Implementation Reference

  • Core handler function for 'get_collection_response'. Makes a GET request to /collections/{collection_id}/responses/{response_id} with optional query params (ids, uid, populate) and returns the response data.
    /**
     * Get details of a specific response in a collection
     */
    async getCollectionResponse(args: any): Promise<ToolCallResponse> {
      const { collection_id, response_id, ...params } = args;
      const response = await this.client.get(
        `/collections/${collection_id}/responses/${response_id}`,
        { params }
      );
      return this.createResponse(response.data);
    }
  • TypeScript interface defining input arguments: extends CollectionIdArg with response_id, ids, uid, populate.
    export interface GetCollectionResponseArgs extends CollectionIdArg {
      response_id: string;
      ids?: boolean;
      uid?: boolean;
      populate?: boolean;
    }
  • Tool definition schema for 'get_collection_response' — includes name, description, and JSON Schema input with collection_id, response_id (required), and optional ids, uid, populate.
    {
      name: 'get_collection_response',
      description: 'Get details of a specific response in a collection',
      inputSchema: {
        type: 'object',
        properties: {
          collection_id: {
            type: 'string',
            description: 'Collection ID',
          },
          response_id: {
            type: 'string',
            description: 'Response ID',
          },
          ids: {
            type: 'boolean',
            description: 'Return only properties that contain ID values',
          },
          uid: {
            type: 'boolean',
            description: 'Return all IDs in UID format',
          },
          populate: {
            type: 'boolean',
            description: 'Return all response contents',
          },
        },
        required: ['collection_id', 'response_id'],
      },
    },
  • Case statement in handleToolCall that routes 'get_collection_response' to the getCollectionResponse method.
    case 'get_collection_response':
      return await this.getCollectionResponse(args);
  • CollectionIdArg interface providing the collection_id field that GetCollectionResponseArgs extends.
    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 responsibility for behavioral disclosure. However, it does not mention that the tool is read-only, what the optional boolean flags (ids, uid, populate) do to the response, or any authentication requirements.

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?

The description is very concise—only one sentence of 9 words. It front-loads the purpose, but could benefit from including more detail without becoming overly long.

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 tool has 5 parameters (2 required) and no output schema. The description does not explain the return format, how the boolean flags affect the response, or the interaction between parameters. This leaves significant gaps for effective tool usage.

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 is 3. The description adds no additional meaning to the parameters beyond the existing schema descriptions, which are minimal but present.

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 (Get), resource (details of a response), and scope (in a collection). It effectively distinguishes from sibling tools like get_collection_request and get_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 is provided on when to use this tool versus alternatives, nor are there any prerequisites or exclusion criteria. The description simply states what the tool does without contextual usage advice.

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