Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

Create Person

affinity_create_person

Add a new contact to Affinity with required first and last names, and optional emails and organization associations. Returns the new person's ID.

Instructions

Create a new person (contact) in Affinity.

This is a V1 API endpoint - creation is NOT available in V2.

Required fields:

  • firstName: Person's first name

  • lastName: Person's last name

Optional fields:

  • emails: Array of email addresses (first becomes primary)

  • organizationIds: Array of organization IDs to associate

Important:

  • Duplicate email addresses will return a 422 error

  • Use affinity_search_persons first to check if person exists

  • Created person can be retrieved via V2 affinity_get_person using returned ID

Returns (JSON): { "id": number, // Use this ID with other tools "first_name": string, "last_name": string, "primary_email": string | null, "emails": string[], "type": 0 // 0 = external contact }

Example workflow:

  1. Search: affinity_search_persons with term="john@example.com"

  2. If not found: affinity_create_person with firstName, lastName, emails

  3. Add note: affinity_add_note with the returned person ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
firstNameYesFirst name (required)
lastNameYesLast name (required)
emailsNoEmail addresses. First email becomes primary_email. Can be empty array.
organizationIdsNoOrganization IDs to associate with this person
responseFormatNoOutput format: "json" or "markdown". Default: "json"
Behavior5/5

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

Annotations indicate write operation (readOnlyHint=false) and not idempotent. Description adds context: V1 only, duplicate email handling, return structure, and example workflow. No contradictions.

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 sections: purpose, API version, required/optional fields, important notes, return example, workflow. Some redundancy but every section adds value.

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?

Comprehensive for a creation tool without output schema. Covers all parameters, error conditions, return format, and integration with other tools (search, get, add note).

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%, but description adds meaning: first email becomes primary, duplicate emails cause 422, organizationIds associate person. Clarifies responseFormat optional.

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 'Create a new person (contact) in Affinity' with specific verb and resource. It distinguishes from siblings like affinity_search_persons and affinity_create_company.

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?

Provides explicit when-to-use: creating a person. Includes workflow: search first, then create if not found. Warns about duplicate emails and suggests using affinity_search_persons before creation.

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