post_v1_crm_contacts

CreateContact adds a person to the caller's org and answers 201 with the stored record.

CreateContact adds a person to the caller's org and answers 201 with the stored record. One of firstName, lastName or email is required, and a companyId must name a company in the same org.


Tool	`post_v1_crm_contacts`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	10
Operation	`POST /v1/crm/contacts`
Product	crm

Arguments

Field	Type	Required	Default	Values	Description
`city`	`string`	—	—	—	City is where the person is based.
`companyId`	`string`	—	—	—	CompanyID links the contact to one of the org's companies.
`email`	`string`	—	—	—	Email is the person's email address.
`firstName`	`string`	—	—	—	FirstName is the person's given name.
`id`	`string`	—	—	—	ID names the contact to update and comes from the path. A create ignores it: the server mints the id.
`jobTitle`	`string`	—	—	—	JobTitle is the person's role at their company.
`lastName`	`string`	—	—	—	LastName is the person's family name.
`linkedinLink`	`string`	—	—	—	Linkedin is the person's LinkedIn URL.
`phone`	`string`	—	—	—	Phone is the person's phone number.
`xLink`	`string`	—	—	—	XLink is the person's X (Twitter) URL.

tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "post_v1_crm_contacts",
         "arguments": {
           "city": "<city>",
           "companyId": "<companyId>",
           "email": "<email>",
           "firstName": "<firstName>",
           "id": "<id>",
           "jobTitle": "<jobTitle>",
           "lastName": "<lastName>",
           "linkedinLink": "<linkedinLink>",
           "phone": "<phone>",
           "xLink": "<xLink>"
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →

The operation behind it

Operation	Route	Product	Summary
`post_v1_crm_contacts`	`POST /v1/crm/contacts`	crm	Adds a person to the caller's org and answers 201 with the stored record.

The same capability over plain HTTP is in the crm API reference, on https://api.hanzo.ai.

All 755 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).

post_v1_crm_contacts

Arguments

Call it

The operation behind it

On this page