Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

Get List Entries

affinity_get_list_entries
Read-onlyIdempotent

Get rows from an Affinity list with field values for companies, people, or opportunities. Supports pagination and field filtering.

Instructions

Get entries (rows) from a specific Affinity list.

Each entry represents a company, person, or opportunity on the list with its field values.

Returns (JSON): { "data": [ { "id": number, // Entry ID (unique within this list) "listId": number, // The list this entry belongs to "creatorId": number, // User who added the entry "type": string, // "company", "person", or "opportunity" "createdAt": string, // When entry was added (ISO timestamp) "entity": { "id": number, // Company/Person/Opportunity ID "name": string, // Entity name "domain": string, // Domain (for companies) "isGlobal": boolean, // Is shared record "fields": [ // Field values (if requested) { "id": string, "type": string, "name": string, "value": { "type": string, "data": any } } ] } } ], "count": number, // Items in response "hasMore": boolean, // More results available "nextCursor": string|null, // Pagination cursor "summary": string // Human-readable summary }

Field Types:

  • enriched: Affinity Data fields (description, employees, funding, etc.)

  • global: Account-wide custom fields

  • list: List-specific fields (Status, Amount, Owners, Priority, etc.)

Important: Fields are nested inside entity.fields, not at the entry level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYesList ID (numeric). Get from affinity_list_lists. Example: "95303"
fieldTypesNoField categories to include. Options: "enriched", "global", "list" (list-specific fields like Status, Amount). Without this, no field data is returned.
fieldIdsNoSpecific field IDs to return. Example: ["field-1022243", "affinity-data-description"]
limitNoNumber of entries 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?

Goes beyond annotations by detailing pagination (hasMore, nextCursor), nesting of fields, and that fieldTypes parameter controls whether data is returned. All behavioral disclosures are consistent with readOnly and idempotent 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?

Well-structured with a clear front-loaded purpose and organized output schema. The extensive JSON example is informative but slightly verbose; however, every element serves a purpose.

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?

Provides a comprehensive view: output format, pagination, field types, and constraints (e.g., default limit, max). No output schema exists, so the description compensates fully. All necessary context for a 6-parameter read tool.

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%, so baseline is 3. Description adds value by explaining the effect of fieldTypes (enriched, global, list) and the nesting of fields, which helps clarify parameter usage beyond the schema descriptions.

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 it retrieves entries from an Affinity list, specifying that entries represent companies, people, or opportunities. Distinguishes from siblings like affinity_get_list (list metadata) and affinity_get_company_list_entries (specific to a company).

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?

Implies usage by describing the tool's action and including field type explanations, but lacks explicit guidance on when to use this tool versus alternatives like affinity_get_company_list_entries or when to avoid using it.

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