Skip to main content
Glama
alludium

Affinity MCP Server

by alludium
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Get Company List Entries

affinity_get_company_list_entries
Read-onlyIdempotent

Retrieve all list entries for a company across all lists, including list-specific, global, enriched, and relationship-intelligence fields.

Instructions

Get all list entries for a company across ALL lists with full field data.

Returns complete list entry data including:

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

  • Global fields (account-wide custom fields)

  • Enriched fields (auto-populated enrichment data)

  • Relationship-intelligence fields (email/calendar derived)

Parameters:

  • companyId: Company ID (required) - get from affinity_search_companies or affinity_get_company

  • cursor: Pagination cursor (optional)

  • limit: Items per page (default 100, max 100)

Returns (JSON): { "entries": [ { "id": number, // List entry ID "listId": number, // Which list this entry is on "creatorId": number, "createdAt": string, // ISO 8601 "fields": [ { "id": "field-1022243", "name": "Status", "type": "list", // "list", "global", "enriched", "relationship-intelligence" "value": { "type": "ranked-dropdown", "data": { "text": "Portfolio", "rank": 7, "color": "purple" } } } ] } ], "count": number, "hasMore": boolean, "nextCursor": string | null, "summary": { "totalEntries": number, "listsWithEntries": number, "fieldsPerEntry": number } }

Note: Returns empty array if company not on any lists (very common).

Use Cases:

  • "Get all deal data for this company across pipelines"

  • "Export company's complete list information"

  • "See Status, Amount, Owners fields for this portfolio company"

Field Types Included:

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

  • global: Account-wide custom fields

  • enriched: Auto-populated enrichment data

  • relationship-intelligence: Email/calendar derived data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdYesCompany ID (numeric). Get from affinity_search_companies or affinity_get_company.
cursorNoPagination cursor from previous response
limitNoItems per page (default 100, max 100)
responseFormatNoOutput format: "json" or "markdown". Default: "json"

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

The description adds value beyond annotations by detailing the return type, empty array behavior for companies not on lists, and the categories of fields included, which are not covered by readOnlyHint, destructiveHint, etc.

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 purpose upfront, followed by return format, parameters, use cases, and field types. It is somewhat lengthy but each 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?

The description is very complete, providing a full JSON response example, covering edge cases (empty array), and detailing all field categories, compensating for the lack of an output schema.

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%, but the description enhances parameter understanding with context like where to obtain companyId, default/limits for limit, and pagination guidance, though responseFormat is only in 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 tool retrieves all list entries for a company across all lists with full field data, distinguishing it from sibling tools like affinity_get_list_entries which are for single lists.

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?

While the description lists use cases and implies scope, it does not explicitly state when to use this tool versus alternatives or when not to use it, leaving the agent to infer from context.

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