Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

Create Company

affinity_create_company

Create a new company in Affinity CRM by providing a name and optional domain. Returns the company ID for use with other tools.

Instructions

Create a new company (organization) in Affinity.

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

Required fields:

  • name: Company name

Optional fields:

  • domain: Primary domain (e.g., "acme.com")

  • domains: Additional domains

Important:

  • Created companies are always custom (global=false)

  • Global companies from Affinity's shared database cannot be created this way

  • Use affinity_search_companies first to check if company exists

  • Created company can be retrieved via V2 affinity_get_company using returned ID

Returns (JSON): { "id": number, // Use this ID with other tools "name": string, "domain": string | null, "domains": string[], "global": false // Always false for created companies }

Example workflow:

  1. Search: affinity_search_companies with term="acme.com"

  2. If not found: affinity_create_company with name, domain

  3. Get full details: affinity_get_company with the returned ID

  4. Add note: affinity_add_note with the returned company ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCompany name (required)
domainNoPrimary domain (e.g., "acme.com")
domainsNoAdditional domains
responseFormatNoOutput format: "json" or "markdown". Default: "json"
Behavior5/5

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

Annotations indicate a write operation (readOnlyHint=false), and the description adds that created companies are always custom (global=false), explains the return format, and mentions the V1/V2 API difference. No contradiction 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections (Required, Optional, Important, Returns, Example Workflow). Every sentence provides value; no fluff.

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?

Covers prerequisites, behavioral traits, return format, and post-creation usage. With no output schema, it fully documents the return object and example workflow, making it complete for the tool's complexity.

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%, so baseline is 3. Description adds value by clarifying domain as 'Primary domain' with an example, and notes the purpose of responseFormat. Slightly above baseline.

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 company (organization) in Affinity,' with a specific verb and resource. It distinguishes from sibling tools like affinity_create_person and affinity_search_companies by mentioning API version differences and suggesting a workflow.

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?

Explicitly advises to use affinity_search_companies first to check existence, notes that global companies cannot be created, and provides an example workflow. Names alternatives and gives clear when-to-use guidance.

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