Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

List Companies

affinity_list_companies
Read-onlyIdempotent

Retrieve company records from Affinity CRM with optional enriched or custom field data, filter by IDs, and paginate results.

Instructions

List companies (organizations) from Affinity CRM.

Returns company records with optional field data. Without fieldTypes parameter, returns only basic info (id, name, domain, domains, isGlobal).

Field Types:

  • enriched: Data from Affinity Data and Dealroom (description, employees, funding, location, LinkedIn, industry, etc.)

  • global: Your account's custom company fields

Important Notes:

  • This endpoint does NOT support text/name filtering

  • To find specific companies: use the 'ids' parameter with known company IDs

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

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

Returns (JSON): { "data": [ { "id": number, // Company ID "name": string, // Company name "domain": string, // Primary domain "domains": string[], // All domains "isGlobal": boolean, // Is shared record "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 }

Example enriched fields returned:

  • affinity-data-description (company description)

  • affinity-data-number-of-employees (employee count)

  • affinity-data-location (city, state, country)

  • affinity-data-total-funding-amount (USD)

  • affinity-data-linkedin-url

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoFilter by specific company IDs. Example: [1514108, 279041073]
fieldTypesNoField categories to include. Options: "enriched" (Affinity Data, Dealroom), "global" (custom fields). Without this, no field data is returned.
fieldIdsNoSpecific field IDs to return. Example: ["affinity-data-description", "affinity-data-location"]
limitNoNumber of companies 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"
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds crucial behavioral details: no text filtering, pagination with max 100 per request, field types (enriched, global), and example return fields. No contradictions.

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 clear sections (Important Notes, Returns JSON example, Example enriched fields). Every sentence adds value, no fluff. Concisely covers all essential information.

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 JSON return structure with example and covers all parameters, behavior, limitations, and pagination. Fully sufficient for an AI agent to use correctly.

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 descriptions. Description adds significant value beyond schema: explains fieldTypes categories, pagination cursor usage, limit default and max, responseFormat options, and provides example enriched field names.

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 companies from Affinity CRM and explicitly distinguishes from siblings by noting it does not support text/name filtering, directing users to affinity_get_list_entries for searching.

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?

Provides explicit when-to-use (listing companies) and when-not-to-use (text/name filtering), with clear alternative (Saved Views via affinity_get_list_entries). Also notes pagination and parameter usage.

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