Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

Get Persons Fields

affinity_get_persons_fields
Read-onlyIdempotent

Retrieves all person field definitions in Affinity CRM, including types, dropdown options, and enrichment sources, for schema discovery and form generation.

Instructions

Retrieve all global (account-wide) field definitions for persons.

This is a V1 API endpoint - persons fields GET is NOT available in V2.

Returns complete schema information for person fields including:

  • Field names and IDs

  • Field types (text, number, dropdown, etc.)

  • Dropdown options (available choices)

  • Multiple value support

  • Enrichment sources (external data providers)

Use Cases:

  • Schema discovery: "What person fields exist in our CRM?"

  • Form generation: Build dynamic forms based on available fields

  • Field validation: Check if input values are valid for dropdown fields

  • Field resolution: Map field IDs to human-readable names

  • Data source tracking: Identify which fields come from enrichment providers

No Parameters Required: This is a simple GET request with no parameters. Returns all global person fields.

Returns (JSON): { "fields": [ { "id": number, // Field identifier "name": string, // Field display name "value_type": number, // 0-9 enum (see types below) "value_type_name": string, // Human-readable type "allows_multiple": boolean, // Can have multiple values "dropdown_options": [...], // Available choices (if dropdown) "enrichment_source": string // e.g., "affinity-data", "crunchbase" } ], "count": number, "by_type": { // Distribution by field type "Dropdown": number, "Text": number, ... }, "by_source": { // Distribution by data source "affinity-data": number, "none": number, ... }, "summary": string }

Field Value Types:

  • 0 = Person: References another person

  • 1 = Organization: References an organization

  • 2 = Dropdown: Single/multi-select from predefined options

  • 3 = Number: Numeric value

  • 4 = Date: Date/timestamp

  • 5 = Location: Geographic location (city, state, country)

  • 6 = Text: Free-form text

  • 7 = Ranked Dropdown: Ordered dropdown (e.g., pipeline stages)

  • 8 = Formula: Computed/calculated value

  • 9 = Interaction: Email/meeting reference

Enrichment Sources:

  • "affinity-data": Affinity's proprietary data

  • "crunchbase": Crunchbase data

  • "dealroom": Dealroom data

  • "none" or null: Custom fields created by your team

Example Use Cases:

  1. Discover all person fields: No parameters needed Returns: Complete list of person field schemas

  2. Find dropdown fields: Filter response by fields that have dropdown_options

  3. Identify enriched fields: Filter by enrichment_source to see external data

  4. Build dynamic forms: Use field definitions to generate input forms programmatically

Response Format: Use responseFormat parameter to get either:

  • "json": Structured data with statistics (default)

  • "markdown": Human-readable formatted output

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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 provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds value by explaining it is a simple GET request, detailing the response structure (field types, enrichment sources), and mentioning the API version limitation. 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?

The description is well-structured with clear sections (purpose, use cases, response format, field types, examples). It is somewhat lengthy but every section adds necessary information. It front-loads the main purpose and is appropriately sized for a schema discovery tool.

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?

Given the simplicity of the tool (one optional parameter, no required params, no output schema), the description covers all necessary context: purpose, usage scenarios, response structure with examples, and even API version limitations. It is fully complete for an AI agent to select and use correctly.

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 the single parameter responseFormat fully defined. The description adds context by explaining its purpose (choose output format), default value ('json'), and concrete use. This exceeds the baseline of 3 for high schema coverage.

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 specifies 'retrieve all global (account-wide) field definitions for persons' with a clear verb and resource. It distinguishes from siblings like affinity_list_persons and affinity_get_organizations_fields by focusing on field schema retrieval, and it highlights that this V1 endpoint is not available in V2.

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

Usage Guidelines4/5

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

The description lists extensive use cases (schema discovery, form generation, field validation, etc.) and provides example scenarios. However, it does not explicitly state when to avoid using this tool or compare it directly to alternatives like affinity_get_field_values or affinity_get_organizations_fields.

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