Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

List Lists

affinity_list_lists
Read-onlyIdempotent

Retrieve all lists from Affinity CRM, including details like ID, name, and type (company, person, or opportunity). Use list IDs to fetch entries.

Instructions

Get all lists in Affinity CRM.

Lists are spreadsheet-like collections containing companies, persons, or opportunities. Each list has custom fields for tracking deals, contacts, etc.

Returns (JSON): { "data": [ { "id": number, // List ID (use for affinity_get_list_entries) "name": string, // List display name "type": string, // "company", "person", or "opportunity" "creatorId": number, // User who created the list "ownerId": number, // User who owns the list "isPublic": boolean // Whether visible to all users } ], "count": number, // Items in response "hasMore": boolean, // More results available "nextCursor": string|null, // Pagination cursor "summary": string // Human-readable summary }

Note: To get list fields/columns, use GET /v2/lists/{listId}/fields (not yet implemented). To get list entries (rows), use affinity_get_list_entries with the list ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of lists 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 indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds detailed JSON output structure, pagination behavior, and notes on response format, providing comprehensive behavioral context beyond 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: clear first sentence, explanatory paragraph, code block for output, and relevant notes. While thorough, it is slightly verbose but not wasteful, earning a 4.

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 output structure, pagination details, and cross-references to related tools. It fully equips an agent to use this tool correctly.

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

Parameters3/5

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

Schema coverage is 100% with parameter descriptions already detailed (e.g., limit default/max, cursor format). The description does not add new parameter-level information, only reinforces existing schema details, so baseline 3 is appropriate.

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 'Get all lists in Affinity CRM' with a specific verb and resource. It distinguishes from sibling tools like affinity_get_list (single list) and mentions related tools for fields and entries.

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 description provides context that lists are spreadsheet-like collections and includes notes on next steps (get fields, get entries). It implicitly differentiates from single-list retrieval tools, but lacks explicit when-not-to-use guidance.

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