Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

Get Companies in Swimlane

affinity_get_companies_in_swimlane
Read-onlyIdempotent

Retrieve companies in a specific pipeline stage (swimlane) from an Affinity list by providing list ID and swimlane ID.

Instructions

Get all companies at a specific pipeline stage (swimlane).

Returns companies filtered by their Status field value in a list.

Important: This tool performs client-side filtering since the Affinity API doesn't support server-side filtering by status. For large lists (>100 entries), use pagination parameters.

Parameters:

  • listId: List ID (required) - get from affinity_list_lists

  • swimlaneId: Swimlane/stage ID (required) - get from affinity_get_swimlanes (this is the dropdownOptionId)

  • cursor: Pagination cursor (optional)

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

Returns (JSON): { "companies": [ { "id": number, "name": string, "domain": string, "isGlobal": boolean, "status": { "text": "Portfolio", "rank": 7, "color": "purple", "dropdownOptionId": number }, "listEntryId": number, "createdAt": string } ], "count": number, "swimlaneText": string, "listName": string, "hasMore": boolean }

Workflow:

  1. Use affinity_list_lists to find lists

  2. Use affinity_get_swimlanes to see available stages

  3. Use this tool to get companies in a specific stage

Use Cases:

  • "Get all companies in the Lead stage"

  • "Show me portfolio companies"

  • "List companies in Meeting Scheduled stage"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYesList ID (numeric). Get from affinity_list_lists.
swimlaneIdYesSwimlane/stage ID (numeric dropdownOptionId). Get from affinity_get_swimlanes.
cursorNoPagination cursor from previous response
limitNoItems per page (default 100, max 100)
responseFormatNoOutput format: "json" or "markdown". Default: "json"
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent. Description adds transparency about client-side filtering and API limitations, which is valuable beyond annotations. No contradiction.

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 headers, bullet points, code block, and use cases. Length is justified by the amount of useful information. Could be slightly shorter but every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (client-side filtering, pagination, workflow), the description is quite complete. Provides sample return JSON, workflow steps, and behavioral notes. No output schema but compensates with detailed return description.

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% with descriptions. Description enhances parameters by explaining how to obtain listId and swimlaneId, default/max for limit, and the role of cursor. Adds context beyond 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 'Get all companies at a specific pipeline stage (swimlane)' with a specific verb and resource. It distinguishes from siblings like affinity_list_companies by focusing on stage filtering, and the workflow helps differentiate.

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?

Provides a clear workflow (list lists, get swimlanes, then this tool) and use cases. Mentions client-side filtering and pagination for large lists. Lacks explicit when-not-to-use instructions but context is sufficient.

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