Skip to main content
Glama
kesslerio

Attio MCP Server

by kesslerio

remove-record-from-list

Remove companies or people from CRM lists such as sales pipelines and lead lists by specifying the list and entry IDs.

Instructions

Remove a company or person from a CRM list (sales pipeline, lead list, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entryIdYesID of the list entry to remove
listIdYesID of the list to remove the record from

Implementation Reference

  • MCP tool handler configuration and execution logic for 'remove-record-from-list'. Validates listId UUID and calls the core removal function.
    removeRecordFromList: {
      name: 'remove-record-from-list',
      handler: async (listId: string, entryId: string) => {
        // UUID validation - hard fail for invalid list IDs
        if (!isValidUUID(listId)) {
          return {
            isError: true,
            content: [
              {
                type: 'text',
                text: `Invalid list_id: must be a UUID. Got: ${listId}`,
              },
            ],
          };
        }
        return await removeRecordFromList(listId, entryId);
      },
      idParams: ['listId', 'entryId'],
    } as ListActionToolConfig,
  • Input schema and description definition for the 'remove-record-from-list' MCP tool.
      name: 'remove-record-from-list',
      description: formatToolDescription({
        capability: 'Remove company or person from list (membership only).',
        boundaries: 'delete underlying record; membership only.',
        requiresApproval: true,
        constraints: 'Requires list UUID, entry UUID (not record UUID).',
        recoveryHint: 'Use get-list-entries to find entry UUID.',
      }),
      inputSchema: {
        type: 'object',
        properties: {
          listId: {
            type: 'string',
            description: 'UUID of the list to remove the entry from',
            example: '550e8400-e29b-41d4-a716-446655440000',
          },
          entryId: {
            type: 'string',
            description: 'UUID of the list entry to remove (not the record ID)',
            example: '770e8400-e29b-41d4-a716-446655440002',
          },
        },
        required: ['listId', 'entryId'],
        additionalProperties: false,
      },
    },
  • Core API implementation: performs DELETE request to Attio API endpoint `/lists/{listId}/entries/{entryId}` to remove the list entry.
    export async function removeRecordFromList(
      listId: string,
      entryId: string,
      retryConfig?: Partial<RetryConfig>
    ): Promise<boolean> {
      const api = getLazyAttioClient();
      const path = `/lists/${listId}/entries/${entryId}`;
    
      return callWithRetry(async () => {
        await api.delete(path);
        return true;
      }, retryConfig);
    }
  • Objects layer wrapper for removeRecordFromList with fallback to direct API DELETE.
    export async function removeRecordFromList(
      listId: string,
      entryId: string
    ): Promise<boolean> {
      try {
        return await removeGenericRecordFromList(listId, entryId);
      } catch (error: unknown) {
        if (process.env.NODE_ENV === 'development') {
          createScopedLogger('objects.lists', 'removeRecordFromList').warn(
            'Generic removeRecordFromList failed',
            {
              message: error instanceof Error ? error.message : 'Unknown error',
            }
          );
        }
    
        const api = getLazyAttioClient();
        const path = `/lists/${listId}/entries/${entryId}`;
    
        await api.delete(path);
        return true;
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool performs a removal operation but doesn't clarify if this is reversible, requires specific permissions, affects related data, or has side effects. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 and includes helpful examples without unnecessary elaboration. Every word earns its place, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on what happens after removal (e.g., confirmation message, error handling), whether the action is logged or reversible, and how it differs from similar tools. Given the complexity of list management in a CRM context, more 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 description coverage is 100%, with both parameters ('entryId' and 'listId') clearly documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as format examples or relationship context, so it meets the baseline for high schema coverage.

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 action ('Remove') and target ('a company or person from a CRM list'), with examples of list types ('sales pipeline, lead list, etc.') that provide helpful context. It doesn't explicitly differentiate from sibling tools like 'delete-record' or 'update-list-entry', which would require a 5.

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 like 'delete-record' (which might permanently delete) or 'update-list-entry' (which might modify rather than remove). The description mentions CRM lists but doesn't specify prerequisites, exclusions, or typical scenarios for removal.

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