Skip to main content
Glama

getSpecCollections

Read-onlyIdempotent

Retrieve paginated collections generated from a specific API specification using its spec ID.

Instructions

Gets all of an API specification's generated collections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
specIdYesThe spec's ID.
elementTypeYesThe `collection` element type.
limitNoThe maximum number of rows to return in the response.
cursorNoThe pointer to the first record of the set of paginated results. To view the next response, use the `nextCursor` value for this parameter.

Implementation Reference

  • The handler function that executes the getSpecCollections tool logic. It calls the Postman API endpoint /specs/{specId}/generations/{elementType} with optional limit/cursor query params for pagination.
    export async function handler(
      args: z.infer<typeof parameters>,
      extra: { client: PostmanAPIClient; headers?: IsomorphicHeaders; serverContext?: ServerContext }
    ): Promise<CallToolResult> {
      try {
        const endpoint = `/specs/${args.specId}/generations/${args.elementType}`;
        const query = new URLSearchParams();
        if (args.limit !== undefined) query.set('limit', String(args.limit));
        if (args.cursor !== undefined) query.set('cursor', String(args.cursor));
        const url = query.toString() ? `${endpoint}?${query.toString()}` : endpoint;
        const options: any = {
          headers: extra.headers,
        };
        const result = await extra.client.get(url, options);
        return {
          content: [
            {
              type: 'text',
              text: `${typeof result === 'string' ? result : JSON.stringify(result, null, 2)}`,
            },
          ],
        };
      } catch (e: unknown) {
        if (e instanceof McpError) {
          throw e;
        }
        throw asMcpError(e);
      }
    }
  • The method name, description, Zod schema (parameters with specId, elementType, limit, cursor), and annotations for the getSpecCollections tool.
    export const method = 'getSpecCollections';
    export const description = "Gets all of an API specification's generated collections.";
    export const parameters = z.object({
      specId: z.string().describe("The spec's ID."),
      elementType: z.literal('collection').describe('The `collection` element type.'),
      limit: z
        .number()
        .int()
        .describe('The maximum number of rows to return in the response.')
        .default(10),
      cursor: z
        .string()
        .describe(
          'The pointer to the first record of the set of paginated results. To view the next response, use the `nextCursor` value for this parameter.'
        )
        .optional(),
    });
    export const annotations = {
      title: "Gets all of an API specification's generated collections.",
      readOnlyHint: true,
      destructiveHint: false,
      idempotentHint: true,
    };
  • Registration of 'getSpecCollections' in the 'full' list of enabled resources (line 17) and the 'minimal' list (line 182), making it available as a tool.
    const full = [
      // Collections
      'createCollection',
      'deleteCollection',
      'generateCollection',
      'getCollection',
      'getCollections',
      'patchCollection',
      'putCollection',
      'getCollectionTags',
      'updateCollectionTags',
      'getCollectionUpdatesTasks',
      'syncCollectionWithSpec',
      'syncSpecWithCollection',
      'generateSpecFromCollection',
      'getGeneratedCollectionSpecs',
      'getSpecCollections',
    
      // Collection Forks
      'getCollectionForks',
      'getSourceCollectionStatus',
      'getCollectionsForkedByUser',
      'pullCollectionChanges',
      'createCollectionFork',
      'mergeCollectionFork',
    
      // Collection Folders
      'createCollectionFolder',
      'deleteCollectionFolder',
      'getCollectionFolder',
      'updateCollectionFolder',
      'transferCollectionFolders',
    
      // Collection Requests
      'createCollectionRequest',
      'deleteCollectionRequest',
      'getCollectionRequest',
      'updateCollectionRequest',
      'transferCollectionRequests',
    
      // Collection Responses
      'createCollectionResponse',
      'deleteCollectionResponse',
      'getCollectionResponse',
      'updateCollectionResponse',
      'transferCollectionResponses',
    
      // Collection Runner
      'runCollection',
    
      // Comments
      'createCollectionComment',
      'deleteCollectionComment',
      'getCollectionComments',
      'updateCollectionComment',
      'updateApiCollectionComment',
      'createFolderComment',
      'deleteFolderComment',
      'getFolderComments',
      'updateFolderComment',
      'createRequestComment',
      'deleteRequestComment',
      'getRequestComments',
      'updateRequestComment',
      'createResponseComment',
      'deleteResponseComment',
      'getResponseComments',
      'updateResponseComment',
      'resolveCommentThread',
    
      // Environments
      'createEnvironment',
      'deleteEnvironment',
      'getEnvironment',
      'getEnvironments',
      'patchEnvironment',
      'putEnvironment',
    
      // Mocks
      'createMock',
      'deleteMock',
      'getMock',
      'getMocks',
      'updateMock',
      'publishMock',
      'unpublishMock',
    
      // Monitors
      'createMonitor',
      'deleteMonitor',
      'getMonitor',
      'getMonitors',
      'updateMonitor',
      'runMonitor',
    
      // Specs
      'createSpec',
      'deleteSpec',
      'getSpec',
      'getAllSpecs',
      'getSpecDefinition',
      'updateSpecProperties',
      'createSpecFile',
      'getSpecFile',
      'getSpecFiles',
      'updateSpecFile',
    
      // Workspaces
      'createWorkspace',
      'deleteWorkspace',
      'getWorkspace',
      'getWorkspaces',
      'updateWorkspace',
      'getWorkspaceGlobalVariables',
      'updateWorkspaceGlobalVariables',
      'getWorkspaceTags',
      'updateWorkspaceTags',
    
      // PAN (Private API Network)
      'listPrivateNetworkWorkspaces',
      'listPrivateNetworkAddRequests',
      'removeWorkspaceFromPrivateNetwork',
      'addWorkspaceToPrivateNetwork',
      'respondPrivateNetworkAddRequest',
    
      // // Documentation
      'publishDocumentation',
      'unpublishDocumentation',
    
      // Tasks and Status
      'getAsyncSpecTaskStatus',
      'getStatusOfAnAsyncApiTask',
    
      // User and Tags
      'getAuthenticatedUser',
      'getTaggedEntities',
    
      // Code Generation
      'getCodeGenerationInstructions',
    
      // Transfer
      'transferCollectionFolders',
      'transferCollectionResponses',
      'transferCollectionResponses',
    
      // 'asyncMergePullCollectionFork' skipped
      // 'asyncMergePullCollectionTaskStatus' skipped
    
      // Duplicate Collection
      'duplicateCollection',
      'getDuplicateCollectionTaskStatus',
      'deleteApiCollectionComment',
      'deleteSpecFile',
      'getEnabledTools',
      'searchPostmanElementsInPublicNetwork',
      'searchPostmanElementsInPrivateNetwork',
    
      // Analytics
      'getAnalyticsData',
      'getAnalyticsMetadata',
    ] as const;
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description adds minimal behavioral context. It does not mention pagination behavior or response details beyond the schema.

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 a single, clear sentence with no filler. It is appropriately sized and front-loaded.

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 details about the return format or pagination behavior. With no output schema, the agent needs more context on what 'generated collections' contains.

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%, so the baseline is 3. The description adds no additional meaning to parameters beyond what is in the schema.

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 verb 'Gets' and the resource 'generated collections' of an API specification, distinguishing it from sibling tools like 'getCollections' and 'getCollection'.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'getCollections' (which likely returns all collections) or 'getCollection' (singular). No exclusions or context are given.

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

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