Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

Get Field Values

affinity_get_field_values
Read-onlyIdempotent

Get all custom field values for any person, organization, opportunity, or list entry. Returns global and list-specific fields for data quality and analysis.

Instructions

Retrieve all field values for a specific entity (person, organization, opportunity, or list entry).

This is a V1 API endpoint - field values GET is NOT available in V2.

Returns complete custom field data for an entity including:

  • Global fields (account-wide custom fields)

  • List-specific fields (pipeline stages, deal amounts, etc.)

  • Field metadata (types, creation/update timestamps)

Use Cases:

  • Get all custom fields for a company: "What data is populated for this company?"

  • Inspect deal pipeline data: "Show me all fields for this list entry"

  • Data quality assessment: "Which companies are missing funding amount?"

  • Field comparison: "Compare field data between two opportunities"

Important: Exactly ONE Entity Parameter Required The API enforces that you must specify exactly one of:

  • person_id: Get field values for a person

  • organization_id: Get field values for an organization/company

  • opportunity_id: Get field values for an opportunity

  • list_entry_id: Get field values for a specific list entry

Providing zero parameters or multiple parameters will result in a 422 error.

Field Types: Field values include a value_type that indicates the data type:

  • 0 = Person (references person ID)

  • 1 = Organization (references organization ID)

  • 2 = Dropdown (single-select text)

  • 3 = Number (numeric value)

  • 4 = Date (ISO timestamp)

  • 5 = Location (city, state, country object)

  • 6 = Text (free-form text)

  • 7 = Ranked Dropdown (pipeline stages with id, text, rank, color)

  • 8 = Formula (computed value)

  • 9 = Interaction (email/meeting reference)

Global vs List-Specific Fields:

  • list_entry_id = null: Global field (applies across all lists)

  • list_entry_id = number: List-specific field (only for that list entry)

Field Name Resolution: Field values only contain field_id. To get field names:

  1. Call GET /fields or GET /fields?list_id={id}

  2. Map field_id to field name

  3. Use the mapping to display human-readable field names

Parameters: Choose exactly ONE:

  • person_id: Person identifier (number)

  • organization_id: Organization/Company identifier (number)

  • opportunity_id: Opportunity identifier (number)

  • list_entry_id: List entry identifier (number)

Returns (JSON): { "fieldValues": [ { "id": number, // Field value ID "field_id": number, // Field definition ID (resolve with GET /fields) "entity_id": number, // Entity this value belongs to "entity_type": number, // 0=person, 1=organization, 2=opportunity "list_entry_id": number | null, // null=global, number=list-specific "value": any, // The actual value (type varies) "value_type": number, // 0-9 (see types above) "value_type_name": string, // Human-readable type name "created_at": string, // ISO timestamp "updated_at": string | null // ISO timestamp or null } ], "count": number, "entity_type": string, // "Person", "Organization", "Opportunity" "summary": string }

Example Use Cases:

  1. Get company custom fields: { "organization_id": 303073231 } Returns: Description, Tech tags, LinkedIn URL, Location, Employee count, etc.

  2. Get deal pipeline fields: { "list_entry_id": 227497865 } Returns: Status (Ranked Dropdown), Owners, Raise Amount, Stage, Female Founders, etc.

  3. Get person fields: { "person_id": 250862100 } Returns: Source of Introduction, custom contact fields, etc.

Error Handling:

  • 422: Must specify exactly one entity parameter

  • 422: Invalid entity ID (entity does not exist)

  • Empty array: Entity exists but has no field values

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idNoPerson ID - Get field values for this person (exactly one entity ID required)
organization_idNoOrganization/Company ID - Get field values for this organization (exactly one entity ID required)
opportunity_idNoOpportunity ID - Get field values for this opportunity (exactly one entity ID required)
list_entry_idNoList Entry ID - Get field values for this list entry, including list-specific fields (exactly one entity ID required)
responseFormatNoOutput format: "json" for structured data or "markdown" for human-readable. Default: "json"
Behavior5/5

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

Adds significant behavioral context beyond annotations: V1-only endpoint, field name resolution requirement, global vs list-specific fields, field type enum, full return structure with JSON example, and error handling. Annotations declare readOnlyHint=true, which is consistent.

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 sections, front-loaded with purpose. Some redundancy (e.g., parameter list repeated), but each section adds value. Could be slightly more concise but informative.

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?

Covers all essential aspects: API version, constraints, data types, return structure (with JSON example), field resolution, error handling. No output schema provided but the JSON example serves as a surrogate. Complete for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with parameter descriptions. The description adds details: exactly one required, consequences of violation, entity-specific examples, and responseFormat enum values. Provides practical guidance beyond the schema.

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 the verb 'Retrieve' and the resource 'field values for a specific entity', distinguishing it from sibling tools like `affinity_get_company` or `affinity_get_list_fields`. It lists the four entity types and uses cases.

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?

Provides explicit constraints ('exactly one entity parameter required'), error conditions (422), and use cases (get company fields, inspect pipeline). Lacks explicit comparison to alternatives but context is sufficient.

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