Skip to main content
Glama
soil-dev

capsulemcp

create_party

Add a new person or organisation to Capsule CRM. Specify type, then provide required fields: person needs first or last name, organisation needs name.

Instructions

Create a new person or organisation in Capsule CRM. For type='person', firstName or lastName is required (one suffices); the name field is silently ignored. For type='organisation', name is required and firstName/lastName/title/jobTitle are silently ignored. Passing organisationId pointing at a non-organisation party (e.g. another person's id) returns 404 'organisation not found' — Capsule filters lookups by type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
firstNameNo
lastNameNo
titleNo
jobTitleNo
organisationIdNoLink person to an existing organisation ID
nameNo
aboutNo
emailAddressesNoAPPEND-ONLY: items are merged into the existing list, never replaced. For atomic add/remove/replace use add_party_email_address and remove_party_email_address_by_id. Passing `[]` here is a silent no-op (does not clear the list and does not advance updatedAt).
phoneNumbersNoAPPEND-ONLY: items are merged into the existing list, never replaced. For atomic add/remove/replace use add_party_phone_number and remove_party_phone_number_by_id.
addressesNoAPPEND-ONLY: items are merged into the existing list, never replaced. For atomic add/remove/replace use add_party_address and remove_party_address_by_id. The `country` field is mapped through Capsule's country dictionary — see `add_party_address.country` for the dictionary edges (small canonical-English-name list; inputs not in the dictionary are REJECTED with 422, not silently dropped).
websitesNoAPPEND-ONLY: items are merged into the existing list, never replaced. For atomic add/remove/replace use add_party_website and remove_party_website_by_id.
ownerIdNoAssign to user ID. On create_party, defaults to the API-token owner when omitted. Once set, this connector cannot clear the owner back to null — use Capsule's web UI for that. Discover IDs via list_users.
Behavior5/5

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

Disclosure is extensive in the absence of annotations. It covers silent field ignoring, append-only list behavior, country validation with examples, ownerId default, and error cases (404 for wrong type). This fully compensates for missing 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 relatively long but well-structured, starting with the core purpose then detailing per-type behavior and array specifics. Every sentence adds value, though slight trimming could improve conciseness without losing information.

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?

Given the complexity of 13 parameters, conditional logic, and append-only arrays, the description is thorough. It covers conditional requirements, behavioral quirks, error conditions, and references sibling tools. No output schema exists, and the description handles what's necessary.

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?

With schema coverage at 46%, the description adds critical meaning: type-dependent required fields, which fields are ignored, append-only details, country dictionary nuances, and ownerId default. This goes well beyond the schema's descriptions.

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 it creates a person or organisation in Capsule CRM, distinguishing between the two types with specific field requirements. It differentiates from sibling tools like update_party and add_party_email_address by focusing on creation and noting append-only behaviors.

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?

Provides explicit guidance on when to use which fields based on type (person vs organisation). It also warns about append-only behavior for arrays and points to dedicated tools for atomic operations. However, it doesn't explicitly state when not to use this tool versus other create tools, missing clear exclusion criteria.

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/soil-dev/capsulemcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server