Skip to main content
Glama
MSPbotsAI

keap-mcp

by MSPbotsAI

keap_create_contact

Create a contact in Keap CRM with email, phone, address, and custom fields. Requires at least one email address or phone number.

Instructions

Create a contact. Must include at least one email address or phone number.

    API: POST /contacts

    Args:
        given_name: First name.
        family_name: Last name.
        email_addresses: List of dicts, e.g. [{"email": "a@b.com", "field": "EMAIL1"}].
        phone_numbers: List of dicts, e.g. [{"number": "555-0100", "field": "PHONE1"}].
        addresses: List of dicts, e.g. [{"line1": "...", "locality": "...", "region": "...",
            "postal_code": "...", "country_code": "US", "field": "BILLING"}].
        custom_fields: List of dicts, e.g. [{"id": 1, "content": "value"}].
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressesNo
given_nameNo
family_nameNo
custom_fieldsNo
phone_numbersNo
email_addressesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the HTTP method (POST) and the validation requirement, but does not mention side effects, error behavior, permissions, idempotency, or what happens on duplicate creation. This is a significant gap for a mutation tool.

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 well-organized with a concise summary, an API reference, and a structured argument list. Each line serves a purpose, but the list format and multi-line address example add some length. It is appropriately sized for the number of parameters and not wasteful.

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

Completeness4/5

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

Given the tool has 6 parameters and no annotations, the description adequately covers all parameters with examples and states the core validation rule. An output schema exists, so return values are not needed. However, it omits any mention of permissions, error handling, or behavior beyond creation, which would improve completeness.

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?

The schema has 0% description coverage, but the description compensates fully. It explains each parameter (given_name, family_name, email_addresses, phone_numbers, addresses, custom_fields) with clear definitions and example structures, making the intended format explicit and actionable.

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 begins with 'Create a contact,' which clearly identifies the specific action and resource. It is distinct from sibling tools like keap_create_opportunity, keap_create_note, and keap_create_task, and the verb+resource pattern is unambiguous.

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?

The description clearly states a prerequisite: 'Must include at least one email address or phone number.' This provides clear context for when the tool can be used. It does not explicitly mention alternatives or when not to use it, but the purpose is self-evident given the sibling tools cover other operations.

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/MSPbotsAI/keap-mcp'

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