Skip to main content
Glama
ptaramona

Conduyt MCP Server

by ptaramona
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

conduyt_create_contact

Create a new CRM contact with email, phone, company, tags, source, and custom fields. Use it to add leads or people to Conduyt so deals, automations, and messaging can target them.

Instructions

Create a new contact in the CRM. Email or phone is recommended but not strictly required.

Input Schema

NameRequiredDescriptionDefault
tagsNoTag UUIDs to apply (tags must already exist — create them with conduyt_create_tag first)
emailNoContact email address
phoneNoPhone number
sourceNoLead source (e.g. 'website', 'referral', 'import') — FIRST-WRITE-WINS acquisition truth for the lead; later inbound events do not overwrite it. 1-100 chars.
companyNoCompany name
lastNameNoLast name
timezoneNoIANA timezone of the lead (e.g. America/Chicago). Omit to let Conduyt derive it from ZIP → phone area code → state (the stored contact carries timezone + timezoneSource).
firstNameNoFirst name
customFieldsNoStructured custom-field values keyed by field key, e.g. { lead_temperature: 'hot', budget: 50000 }. Define fields first with conduyt_create_custom_field (entity 'contact').
masterStatusNoLifecycle status of the LEAD (master record), distinct from any deal's status: 'open' (default), 'won', 'lost', 'abandoned', 'disqualified', or an account-defined custom status. A terminal status (won/lost/abandoned/disqualified) SILENCES all outbound automations for this contact — drips, sequences, and scheduled sends stop. Use conduyt_get_lifecycle_settings to see the account's configured statuses.
custom_fieldsNoAlias for customFields (snake_case). Provide only one of customFields / custom_fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.71.0

TDQS

B3.3/5.0
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 disclosure burden for a mutation tool. It says nothing about duplicate detection, what happens when no identifying field is supplied, whether permission checks apply, or what side effects creation triggers (e.g. automations enrolling the new lead). 'Create' alone is insufficient for a write operation here.

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?

Two short sentences, operation stated first, caveat second. No filler, no restatement of the tool name, nothing that could be cut without losing information.

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 an 11-parameter create tool with nested objects, no annotations, and no output schema, the description is thin: it does not clarify return content (e.g. the created contact ID), duplicate handling, or the fact that tags/custom field definitions must pre-exist (that lives only in the schema text). It leaves meaningful gaps relative to 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 the baseline is 3. The description adds value beyond it by flagging that email/phone are the identity-bearing fields and are recommended rather than required — a distinction the schema cannot express since no parameters are marked required. That single sentence steers the agent away from creating an unidentifiable contact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Create a new contact in the CRM.' The operation is unmistakable and clearly distinct from update_contact, delete_contact, and import tools. It stops short of naming which sibling to use for bulk/existing-record cases, but the purpose itself 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 Guidelines3/5

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

The one usage hint given — email or phone recommended but not required — is genuinely useful given that all 11 params are optional. However, it doesn't say when to prefer this tool over conduyt_import_contacts, conduyt_ai_import_contacts, or conduyt_update_contact for an existing record.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools