Skip to main content
Glama
BusyBee3333

Keap MCP Server

by BusyBee3333

keap_create_contact

Add a new contact to Keap CRM, including name, email, phone, address, tags, and custom fields, to organize customer information.

Instructions

Create a new contact in Keap with email, name, phone, address, tags, and custom fields

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity
emailNoPrimary email address
phoneNoPrimary phone number
stateNoState/Region
countryNoCountry code (e.g., US)
tag_idsNoArray of tag IDs to apply
owner_idNoUser ID of contact owner
job_titleNoJob title
given_nameNoFirst name
family_nameNoLast name
postal_codeNoPostal/ZIP code
company_nameNoCompany name
address_line1NoStreet address line 1
address_line2NoStreet address line 2
custom_fieldsNoCustom field values [{id, content}]
opt_in_reasonNoReason for opt-in (required for GDPR)
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states the creation action without mentioning side effects, duplicate handling, authentication needs, or error conditions.

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?

The description is a single concise sentence of 15 words, front-loading the action and avoiding redundancy. Every word is informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 16 parameters and no output schema, the description lacks information about return values, validation rules, and behavioral contexts, making it insufficient for confident agent use.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description enumerates broad categories (email, name, phone, address, tags, custom fields) but does not add meaning beyond the schema's detailed 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 the tool creates a new contact, specifying key fields like email, name, phone, address, tags, and custom fields. It distinguishes from sibling tools like keap_update_contact and keap_merge_contacts by emphasizing creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention handling existing contacts, prerequisites, or scenarios where keap_update_contact would be more appropriate.

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/BusyBee3333/keap-mcp-2026-complete'

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