Skip to main content
Glama
kesslerio

Attio MCP Server

by kesslerio

list-notes

Read-onlyIdempotent

Retrieve notes for any CRM record type including companies, people, deals, or tasks by specifying the record ID and resource type.

Instructions

Get notes for any record type (companies, people, deals)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return
offsetNoNumber of results to skip for pagination
parent_record_idNoAlias for record_id (backward compatibility)
record_idNoRecord ID to list notes for
resource_typeYesType of resource to operate on (companies, people, lists, records, tasks)

Implementation Reference

  • Primary handler function executing the list-notes tool logic: fetches notes from Attio API /v2/notes using GET with query parameters for parent resource and record.
    export async function handleListNotes(
      client: HttpClient,
      params: {
        resource_type: 'companies' | 'people' | 'deals';
        record_id: string;
        limit?: number;
        offset?: number;
      }
    ): Promise<ToolResult> {
      try {
        const { resource_type, record_id, limit = 10, offset = 0 } = params;
    
        // Notes API uses GET with query params, not POST
        const queryParams = new URLSearchParams({
          parent_object: resource_type,
          parent_record_id: record_id,
          limit: String(limit),
          offset: String(offset),
        });
    
        const response = await client.get<AttioApiResponse<AttioNote[]>>(
          `/v2/notes?${queryParams.toString()}`
        );
    
        const notes = response.data.data;
    
        if (!notes || notes.length === 0) {
          return structuredResult(
            [],
            `No notes found for ${resource_type} ${record_id}`
          );
        }
    
        const lines = notes.map((note) => {
          const noteId = note.id?.note_id || 'unknown';
          const title = note.title || 'Untitled';
          const preview = (note.content_plaintext || '').slice(0, 100);
          return `- ${title} (ID: ${noteId})\n  ${preview}${preview.length >= 100 ? '...' : ''}`;
        });
    
        return structuredResult(
          notes,
          `Notes for ${resource_type} ${record_id}:\n${lines.join('\n')}`
        );
      } catch (error) {
        const { message, details } = extractErrorInfo(error);
        return errorResult(message || 'Failed to list notes', details);
      }
    }
  • Registration of list-notes in the central tool handler dispatcher map.
      'list-notes': async (client, params) =>
        handleListNotes(client, params as Parameters<typeof handleListNotes>[1]),
    };
  • Input schema, description, and annotations defining the list-notes tool interface.
    export const listNotesDefinition: ToolDefinition = {
      name: 'list-notes',
      description: formatDescription({
        capability: 'Retrieve notes for a record with timestamps',
        boundaries: 'create or modify notes; read-only',
        constraints: 'Requires resource_type, record_id; sorted by creation date',
        recoveryHint: 'If empty, verify record has notes with records_get_details',
      }),
      inputSchema: {
        type: 'object',
        properties: {
          resource_type: {
            type: 'string',
            enum: ['companies', 'people', 'deals'],
            description: 'Type of resource to list notes for',
          },
          record_id: {
            type: 'string',
            description: 'Record ID to list notes for',
          },
          ...PAGINATION_SCHEMA,
        },
        required: ['resource_type', 'record_id'],
      },
      annotations: {
        readOnlyHint: true,
      },
    };
  • Export and registration of listNotesDefinition in coreToolDefinitions map.
    'list-notes': listNotesDefinition,
  • Universal tool configuration registration for list-notes in main application handlers.
    'list-notes': listNotesConfig,
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows this is a safe, repeatable read operation. The description adds context about supporting 'any record type' with examples, but doesn't disclose behavioral traits like pagination behavior (implied by limit/offset), rate limits, authentication needs, or what happens when no notes exist. With annotations covering safety, a 3 is appropriate.

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 purpose. Every word earns its place by specifying the action ('Get'), resource ('notes'), and scope ('any record type') with clarifying examples. There's zero waste or redundancy.

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?

For a read-only listing tool with good annotations (readOnlyHint, idempotentHint) and full schema coverage, the description is minimally adequate. However, without an output schema, it doesn't explain what the returned notes look like (structure, fields, ordering). The description covers the basic purpose but leaves return format unspecified, which is a gap given the tool's complexity.

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 all parameters are documented in the schema. The description mentions 'any record type' which aligns with the resource_type enum, but adds no additional semantic context beyond what the schema provides. With complete schema coverage, the baseline 3 is appropriate.

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 tool's purpose as 'Get notes for any record type' with specific examples (companies, people, deals). It uses a specific verb ('Get') and resource ('notes'), but doesn't explicitly distinguish this from sibling tools like 'create-note' or 'search-by-content' which might also involve notes.

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 sibling tools like 'search-by-content' (which might search note content) or 'create-note' (which creates notes), nor does it specify prerequisites or appropriate contexts for using this listing tool.

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