Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

Get Organizations Fields

affinity_get_organizations_fields
Read-onlyIdempotent

Retrieve all global field definitions for organizations in your CRM. Use this to discover schema, generate dynamic forms, or validate field inputs.

Instructions

Retrieve all global (account-wide) field definitions for organizations/companies.

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

Returns complete schema information for organization fields including:

  • Field names and IDs

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

  • Dropdown options (available choices)

  • Multiple value support

  • Enrichment sources (external data providers like Crunchbase, Dealroom)

Use Cases:

  • Schema discovery: "What company 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

  • Integration planning: Understand what data is available for export/sync

No Parameters Required: This is a simple GET request with no parameters. Returns all global organization 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., "crunchbase", "dealroom" } ], "count": number, "by_type": { // Distribution by field type "Dropdown": number, "Text": number, "Number": number, ... }, "by_source": { // Distribution by data source "crunchbase": number, "dealroom": number, "affinity-data": number, "none": number }, "custom_fields": number, // Count of non-enriched fields "enriched_fields": number, // Count of enriched fields "summary": string }

Field Value Types:

  • 0 = Person: References a person

  • 1 = Organization: References another organization

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

  • 3 = Number: Numeric value (funding, employees, revenue, etc.)

  • 4 = Date: Date/timestamp (founding date, last contact, etc.)

  • 5 = Location: Geographic location (HQ, offices)

  • 6 = Text: Free-form text (description, notes)

  • 7 = Ranked Dropdown: Ordered dropdown (stages, priorities)

  • 8 = Formula: Computed/calculated value

  • 9 = Interaction: Email/meeting reference

Enrichment Sources:

  • "crunchbase": Company data from Crunchbase (funding, employees, investors)

  • "dealroom": European startup data from Dealroom

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

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

Example Use Cases:

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

  2. Find enriched fields: Filter response by enrichment_source to see external data

  3. Identify custom fields: Filter by enrichment_source = "none" to see team-created fields

  4. Get dropdown options: Filter by fields with dropdown_options to see valid choices

  5. Plan data exports: Understand complete schema before building integrations

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"
Behavior5/5

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

Annotations indicate readOnlyHint=true and destructiveHint=false, and the description adds details about being a simple GET request with a structured response. It provides comprehensive information about field types, enrichment sources, and example outputs, fully aligning with and extending the 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 (Use Cases, Returns, Field Value Types, Enrichment Sources, Examples) and front-loaded with the main purpose. It is somewhat lengthy but every section adds value.

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?

For a simple GET tool with no required parameters and no output schema, the description is extremely complete. It covers field types, enrichment sources, response structure, and example use cases, leaving no ambiguity.

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% for the single parameter (responseFormat). The description adds meaning by explaining its purpose, valid values (json/markdown), and default behavior, which is helpful beyond the schema alone.

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 'Retrieve all global (account-wide) field definitions for organizations/companies' and specifies it returns complete schema information. It distinguishes itself from sibling tools like affinity_get_persons_fields by targeting organizations specifically.

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 'Use Cases' section lists explicit scenarios like schema discovery and form generation. It notes 'No Parameters Required' and explains the optional responseFormat parameter. While it doesn't explicitly say when not to use, the context from sibling tools makes it clear this is for schema retrieval, not field values.

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