Skip to main content
Glama
kesslerio

Attio MCP Server

by kesslerio

get-lists

Retrieve all CRM lists from Attio including sales pipelines, lead stages, and customer segments to organize and manage customer relationship data.

Instructions

Get all CRM lists from Attio (sales pipelines, lead stages, customer segments, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core implementation of the get-lists tool handler. Fetches all lists from the Attio API using the generic or direct API client, with fallback handling and error logging.
    export async function getLists(
      objectSlug?: string,
      limit: number = 20
    ): Promise<AttioList[]> {
      try {
        return await getGenericLists(objectSlug, limit);
      } catch (error: unknown) {
        const errorMessage = getErrorMessage(error) ?? 'Unknown error';
        if (process.env.NODE_ENV === 'development') {
          createScopedLogger('objects.lists', 'getLists').warn(
            'Generic getLists failed',
            { errorMessage }
          );
        }
    
        const api = getLazyAttioClient();
        let path = `/lists?limit=${limit}`;
    
        if (objectSlug) {
          path += `&objectSlug=${objectSlug}`;
        }
    
        const response = await api.get(path);
        return asListArray(extract<AttioList[]>(response));
      }
    }
  • Registers the 'get-lists' tool configuration, specifying name, handler function, and result formatter. This config is imported into the central tool registry.
    getLists: {
      name: 'get-lists',
      handler: getLists,
      formatResult: (results: AttioList[]) => {
        // Return JSON string - dispatcher will convert to JSON content
        return JSON.stringify(Array.isArray(results) ? results : []);
      },
    } as GetListsToolConfig,
  • Defines the tool schema including name, description, and empty input schema (no parameters required). Used for MCP tool discovery.
    {
      name: 'get-lists',
      description: formatToolDescription({
        capability:
          'Retrieve all CRM lists (sales pipelines, lead stages, customer segments).',
        boundaries: 'create or modify lists, only reads existing lists.',
        constraints: 'Returns all lists visible to the authenticated workspace.',
        recoveryHint: 'Use get-list-details to inspect individual list schemas.',
      }),
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false,
      },
    },
  • Central tool registry where listsToolConfigs (containing get-lists) is registered under ResourceType.LISTS for exposure to MCP clients.
    export const TOOL_CONFIGS = USE_UNIVERSAL_TOOLS_ONLY
      ? {
          // Universal tools for consolidated operations (Issue #352)
          UNIVERSAL: universalToolConfigs,
          // Lists are relationship containers - always expose them (Issue #470)
          [ResourceType.LISTS]: listsToolConfigs,
          // Workspace members for user discovery (Issue #684)
          [ResourceType.WORKSPACE_MEMBERS]: workspaceMembersToolConfigs,
        }
      : {
          // Legacy resource-specific tools (deprecated, use DISABLE_UNIVERSAL_TOOLS=true to enable)
          [ResourceType.COMPANIES]: companyToolConfigs,
          [ResourceType.PEOPLE]: peopleToolConfigs,
          [ResourceType.DEALS]: dealToolConfigs,
          [ResourceType.LISTS]: listsToolConfigs,
          [ResourceType.TASKS]: tasksToolConfigs,
          [ResourceType.RECORDS]: recordToolConfigs,
          [ResourceType.WORKSPACE_MEMBERS]: workspaceMembersToolConfigs,
          GENERAL: generalToolConfigs,
          // Add other resource types as needed
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 mentions 'Get all CRM lists' but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires authentication, rate limits, pagination, or what the return format might be. For a tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that front-loads the core action ('Get all CRM lists') and includes helpful examples without unnecessary elaboration. Every word earns its place, making it appropriately sized and well-structured.

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's low complexity (0 parameters, no output schema), the description is adequate but incomplete. It specifies what is retrieved but lacks details on behavioral aspects like safety, performance, or output format. With no annotations and no output schema, the description should do more to compensate, but it meets minimum viability for a simple retrieval tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description adds value by specifying 'all CRM lists from Attio' and providing examples, which clarifies the resource scope beyond what the empty schema indicates. Baseline for 0 parameters is 4, and the description compensates appropriately.

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 'all CRM lists from Attio', with examples like 'sales pipelines, lead stages, customer segments' that help clarify scope. However, it doesn't explicitly differentiate from sibling tools like 'get-list-details' or 'get-list-entries', which might retrieve specific list information rather than all lists.

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 'get-list-details' or 'filter-list-entries'. It lacks context on prerequisites, exclusions, or comparisons with sibling tools, leaving the agent to infer usage based on tool names 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