Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

Add Note

affinity_add_note

Create notes attached to companies, persons, or opportunities in Affinity CRM. Supports plain text or HTML content for rich formatting.

Instructions

Create a new note attached to companies, persons, or opportunities in Affinity.

This is a V1 API endpoint.

IMPORTANT: Notes are add-only. Edit and delete are not supported by this MCP.

Required:

  • content: Note text (plain or HTML)

  • At least ONE of: companyIds, personIds, or opportunityIds

Optional:

  • contentType: "text" (default) or "html" for rich formatting

HTML Content Examples:

  • Bold: important

  • Italic: emphasis

  • Links: Pitch Deck

  • Lists: Item 1Item 2

Returns (JSON): { "success": true, "note": { "id": number, // New note ID "content": string, "creator_id": number, "organization_ids": number[], "person_ids": number[], "opportunity_ids": number[], "created_at": string // ISO 8601 } }

Example - Add note with link to company: { "content": "Received pitch deck: View Deck", "companyIds": [223449211], "contentType": "html" }

Use Cases:

  • Record meeting notes

  • Add document links (Google Drive, Dropbox)

  • Log call summaries

  • Document investment decisions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesNote content (required). Plain text or HTML depending on contentType.
companyIdsNoCompany IDs to attach note to. Get IDs from affinity_search_companies.
personIdsNoPerson IDs to attach note to. Get IDs from affinity_search_persons.
opportunityIdsNoOpportunity IDs to attach note to. Get IDs from affinity_list_opportunities.
contentTypeNoContent type: "text" (default) or "html" for rich formatting with links, bold, etc.
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 mutability (readOnlyHint=false, destructiveHint=false). The description adds critical behavioral context: notes are add-only, no edit or delete support, and provides a detailed return JSON structure. 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?

The description is well-structured with sections, front-loaded with purpose and important constraints, and uses examples. Slightly verbose with 'This is a V1 API endpoint' but overall efficient.

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?

For a tool with 6 parameters, no output schema, and moderate complexity, the description covers all aspects: required/optional parameters, return format, examples, use cases, and cross-references to sibling tools for ID lookups. Very complete.

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

Parameters5/5

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

Schema coverage is 100% and descriptions are present, but the description adds significant value: clarifies required combination of parameters, provides HTML examples, a full example with companyIds, and cross-references sibling tools for ID retrieval.

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 creates a new note attached to companies, persons, or opportunities, and specifies it's a V1 API endpoint. It distinguishes from sibling tools like affinity_list_company_notes which are read-only listing operations.

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 explicitly warns that notes are add-only (no edit/delete), lists required and optional parameters, and provides use cases. It does not explicitly mention alternatives for editing/deleting but implies through 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