Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

List Company Notes

affinity_list_company_notes
Read-onlyIdempotent

Retrieve all notes for a company in Affinity. Returns HTML content, creator, timestamps, and note type (entity or interaction) with pagination support.

Instructions

List all notes attached to a specific company in Affinity.

This is a V2 BETA endpoint - API may change.

Returns notes with HTML content, creator information, and timestamps.

Parameters:

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

  • cursor: Pagination cursor from previous response

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

Returns (JSON): { "notes": [ { "id": number, "content": { "html": string }, "creator": { "id": number, "firstName": string, "lastName": string, "primaryEmailAddress": string }, "createdAt": string, // ISO 8601 "type": "entities" | "interaction" } ], "count": number, "hasMore": boolean, "nextCursor": string | null }

Note Types:

  • "entities": Note attached directly to company/person

  • "interaction": Note attached to a meeting or email

Example: Get notes for Sure Valley Ventures (ID: 223449211)

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 20, max 100)
responseFormatNoOutput format: "json" or "markdown". Default: "json"
Behavior5/5

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

In addition to annotations (readOnlyHint true, idempotentHint true), the description explains it's a V2 beta endpoint, details the return structure (HTML content, creator, timestamps), pagination, and note types. No contradictions with 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 with sections for Parameters, Returns, Note Types, and Example, front-loading the purpose. While somewhat lengthy, each section adds value without redundancy.

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 100% schema coverage for 4 parameters, annotations present, and no output schema, the description adequately explains pagination, note types, and provides an example. It lacks error handling or rate limit info but is sufficient for the tool's simplicity.

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%, so baseline is 3. The description adds minor context (companyId source, cursor from previous response, limit defaults) but omits the responseFormat parameter present in the schema, reducing value beyond what schema provides.

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 all notes attached to a specific company in Affinity', specifying the verb (list), resource (notes), and scope (specific company). This distinguishes it from sibling tools like affinity_add_note and affinity_list_person_notes.

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 on what the tool returns and includes an example, but it does not explicitly state when not to use or compare with alternatives. However, the tool's name and context make its purpose clear among siblings.

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