Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

List Persons

affinity_list_persons
Read-onlyIdempotent

List persons from Affinity CRM with optional enriched, custom, or relationship-intelligence fields. Retrieve by specific IDs or paginate through all contacts.

Instructions

List persons (contacts) from Affinity CRM.

Returns person records with optional field data. Without fieldTypes parameter, returns only basic info (id, firstName, lastName, primaryEmailAddress, emailAddresses, type).

Field Types:

  • enriched: Data from Affinity Data (8 fields: job title, organization, location, phone, LinkedIn, etc.)

  • global: Your account's custom person fields

  • relationship-intelligence: Email/calendar derived data (9 fields: first/last email, events, etc.)

Important Notes:

  • This endpoint does NOT support text/name filtering

  • To find specific persons: use the 'ids' parameter with known person IDs

  • To search/filter persons: use Saved Views via affinity_get_list_entries

  • Returns max 100 persons per request; use cursor for pagination

  • type="internal" means person is in your organization

Returns (JSON): { "data": [ { "id": number, // Person ID "firstName": string, // First name "lastName": string, // Last name "primaryEmailAddress": string, // Main email "emailAddresses": string[], // All emails "type": string, // "internal" or "external" "fields": [...] // Field data (if requested) } ], "count": number, // Items in response "hasMore": boolean, // More results available "nextCursor": string|null, // Pagination cursor "summary": string // Human-readable summary }

Enriched fields (8):

  • affinity-data-current-job-title, affinity-data-current-organization

  • affinity-data-job-titles, affinity-data-industry

  • affinity-data-location, affinity-data-phone-number

  • affinity-data-linkedin-url, companies (Organizations)

Relationship Intelligence fields (9):

  • first-email, last-email, last-contact

  • first-event, last-event, next-event

  • first-chat-message, last-chat-message

  • source-of-introduction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoFilter by specific person IDs. Example: [66880587, 142768223]
fieldTypesNoField categories to include. Options: "enriched" (Affinity Data), "global" (custom fields), "relationship-intelligence" (email/calendar data). Without this, no field data is returned.
fieldIdsNoSpecific field IDs to return. Example: ["affinity-data-current-job-title", "last-email"]
limitNoNumber of persons to return per page. Default: 100, Max: 100
cursorNoPagination cursor from previous response (pagination.nextPageToken)
responseFormatNoOutput format: "json" for structured data or "markdown" for human-readable. Default: "json"
Behavior4/5

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

Annotations already indicate read-only, idempotent behavior. Description adds important behavioral details: no text filtering, max 100 results per request, and field types. No contradictions with annotations.

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?

Well-structured with clear sections (overview, notes, returns, field lists). Every part adds value, though slightly lengthy. Front-loaded with main purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive: covers desired functionality, limitations, pagination, field choices, and provides a sample response. No output schema but description compensates with JSON example and field lists.

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?

Schema coverage is 100% with descriptions. Description adds extra value by listing the exact enriched and relationship-intelligence fields, and explaining the type parameter's meaning ('internal' vs 'external').

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 it lists persons from Affinity CRM and distinguishes from siblings by noting it does not support text filtering, unlike search tools, and provides alternatives like using 'ids' or saved views.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when not to use (no text/name filtering) and provides alternatives: use 'ids' for known persons or affinity_get_list_entries for saved views. Also explains pagination and type field meaning.

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/alludium/affinity-mcp-server'

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