Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

List Opportunities

affinity_list_opportunities
Read-onlyIdempotent

Retrieve a list of opportunities from Affinity CRM, including IDs, names, and list IDs. Use this to discover deals or fundraising leads for further detail retrieval.

Instructions

List opportunities from Affinity CRM.

Opportunities represent deals, fundraising leads, or other tracked items that belong to opportunity-type lists.

Returns (JSON): { "data": [ { "id": number, // Opportunity ID "name": string, // Opportunity name "listId": number // The list this opportunity belongs to } ], "count": number, // Items in response "hasMore": boolean, // More results available "nextCursor": string|null, // Pagination cursor "summary": string // Human-readable summary }

Important Notes:

  • Opportunities only return basic info (id, name, listId)

  • To get field data (Status, Amount, etc.), use affinity_get_list_entries with the listId

Example workflow:

  1. Call affinity_list_opportunities to find opportunities

  2. Use the listId to call affinity_get_list_entries with fieldTypes: ["list"] to get field values

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoFilter by specific opportunity IDs. Example: [87195214]
limitNoNumber of opportunities 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"
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that only basic info is returned, includes pagination structure, and notes that opportunities belong to opportunity-type lists. This adds meaningful 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-organized with sections, but slightly lengthy. All content is relevant and adds value. It could be marginally more concise, but still effective.

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?

No output schema, but description includes a JSON example with all fields (data, count, hasMore, nextCursor, summary). It explains limitations and linking to other tools. Combined with annotations, it is fairly complete for a list tool.

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 clear parameter descriptions (e.g., ids example, limit range). The description does not add additional parameter meaning, but the schema itself is sufficient. 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 'List opportunities from Affinity CRM' and defines opportunities as deals/fundraising leads. It distinguishes from sibling tools like affinity_get_opportunity (single) and affinity_get_list_entries (field data).

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?

The description explicitly tells when to use this tool (basic info) and when to use affinity_get_list_entries for field data. It provides an example workflow, making selection effortless.

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