Skip to main content
Glama
kesslerio

Attio MCP Server

by kesslerio

get-list-details

Retrieve detailed configuration and structure information for CRM lists, including pipeline stages and field settings, to understand list organization and data management.

Instructions

Get details for a specific CRM list (pipeline stages, field configuration, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYesID of the list to get details for

Implementation Reference

  • Tool registration config for 'get-list-details', including thin handler wrapper calling getListDetails and JSON formatter.
    getListDetails: {
      name: 'get-list-details',
      handler: async (listId: string) => {
        // Let Attio API decide if list ID is valid (supports UUIDs and slugs)
        return await getListDetails(listId);
      },
      formatResult: (result: AttioList) => {
        // Return JSON string
        return JSON.stringify(result);
      },
    } as ToolConfig,
  • Tool definition including description and input schema for validating listId parameter.
    {
      name: 'get-list-details',
      description: formatToolDescription({
        capability:
          'Retrieve schema and configuration for a specific list (stages, fields, attributes).',
        boundaries: 'modify list structure or retrieve list entries.',
        constraints: 'Requires valid list UUID or slug; accepts both formats.',
        recoveryHint:
          'Use get-lists to discover available list IDs and slugs first.',
      }),
      inputSchema: {
        type: 'object',
        properties: {
          listId: {
            type: 'string',
            description: 'ID or slug of the list to get details for',
            example: 'sales-pipeline',
          },
        },
        required: ['listId'],
        additionalProperties: false,
      },
    },
  • Core handler function that fetches list details via generic or direct Attio API call with comprehensive error handling for 404, 422, etc.
    export async function getListDetails(listId: string): Promise<AttioList> {
      try {
        return await getGenericListDetails(listId);
      } catch (error: unknown) {
        const errorMessage = getErrorMessage(error) ?? 'Unknown error';
        if (process.env.NODE_ENV === 'development') {
          createScopedLogger('objects.lists', 'getListDetails').warn(
            'Generic getListDetails failed',
            { errorMessage }
          );
        }
    
        const api = getLazyAttioClient();
        const path = `/lists/${listId}`;
    
        try {
          const response = await api.get(path);
          const extracted = extract<AttioList>(response);
          return ensureListShape(extracted);
        } catch (apiError: unknown) {
          const status = getErrorStatus(apiError);
          if (status === 404) {
            throw new EnhancedApiError('Record not found', 404, path, 'GET', {
              resourceType: 'lists',
              recordId: String(listId),
              httpStatus: 404,
              documentationHint: 'Use search-lists to find valid list IDs.',
            });
          }
          if (status === 422) {
            const { InvalidRequestError } = await import(
              '../../errors/api-errors.js'
            );
            throw new InvalidRequestError(
              'Invalid parameter(s) for list operation',
              '/lists',
              'GET'
            );
          }
    
          const code = typeof status === 'number' ? status : 500;
          throw new EnhancedApiError(
            getErrorMessage(apiError) ?? 'List retrieval failed',
            code,
            path,
            'GET',
            {
              resourceType: 'lists',
              recordId: String(listId),
              httpStatus: code,
            }
          );
        }
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a read operation ('Get'), but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or what happens if the list ID is invalid. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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 a single, efficient sentence that front-loads the core purpose. It avoids unnecessary words and directly states what the tool does. The parenthetical examples add useful context without verbosity.

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?

Given the tool has one parameter with full schema coverage but no annotations or output schema, the description is minimally adequate. It clarifies the tool's focus on list details (not entries or records), but doesn't address behavioral aspects or output format. For a read-only tool with simple inputs, this is acceptable but leaves room for improvement.

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%, with the single parameter 'listId' fully documented in the schema. The description adds no additional parameter semantics beyond implying the tool fetches details for a list, which is already clear from the schema. This meets the baseline of 3 when schema coverage is high.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and resource 'details for a specific CRM list', with examples of what details might include (pipeline stages, field configuration). It distinguishes from siblings like 'get-lists' (which lists multiple lists) and 'get-record-details' (which focuses on records rather than lists). However, it doesn't explicitly differentiate from 'get-detailed-info' which might overlap in purpose.

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. It doesn't mention prerequisites (e.g., needing a valid list ID), exclusions, or compare to similar tools like 'get-detailed-info' or 'get-list-entries'. The agent must infer usage from the name and context alone.

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/kesslerio/attio-mcp-server'

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