Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

Get Person

affinity_get_person
Read-onlyIdempotent

Retrieve a person's details by ID from Affinity CRM, including custom fields and enriched data like job title or location.

Instructions

Get a single person by ID from Affinity CRM.

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

Field Types:

  • enriched: Data from Affinity Data (job title, organization, location, phone, LinkedIn)

  • global: Your account's custom person fields

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

Returns (JSON): { "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) { "id": string, // Field ID "type": string, // "enriched", "global", or "relationship-intelligence" "name": string, // Field name "value": { "type": string, // Value type "data": any // Field value } } ] }

Example field IDs you can request:

  • affinity-data-current-job-title

  • affinity-data-current-organization

  • affinity-data-location

  • last-email, first-email

  • source-of-introduction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
personIdYesPerson ID (numeric). Get IDs from affinity_list_persons or affinity_get_list_entries.
fieldTypesNoField categories to include. Options: "enriched", "global", "relationship-intelligence".
fieldIdsNoSpecific field IDs to return. Example: ["affinity-data-current-job-title", "last-email"]
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 declare readOnlyHint=true, idempotentHint=true. Description adds valuable context about field types (enriched, global, relationship-intelligence) and example field IDs, enhancing transparency without contradiction.

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?

Well-structured with sections for description, field types, return format, and examples. Front-loaded with key purpose, and every sentence adds value without redundancy.

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?

Despite no output schema, the description provides a complete return JSON example, covers all parameters, and explains field types. Adequate for a simple get-by-ID operation.

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 covers all parameters (100% coverage), baseline 3. Description adds meaningful examples (field IDs), categorization of fieldTypes, and context for personId (where to find IDs), exceeding baseline.

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?

Clearly states 'Get a single person by ID from Affinity CRM' and distinguishes from sibling tools like affinity_list_persons (list) and affinity_create_person (create). The specific verb 'get' and resource 'person by ID' make the purpose unambiguous.

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

Usage Guidelines3/5

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

Description implies use when a specific person's details are needed, but lacks explicit when-not or alternatives. Sibling tools exist (e.g., affinity_search_persons), but no guidance on choosing between them is provided.

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