Typeform MCP

Create one or more contacts lists (segments) in the contacts database in a single call. always use this tool to create contacts lists, even when creating just one — pass a single-element `lists` array. ## use cases - create one or several segments to organize contacts - create lists with custom filter, sort, or table column settings ## inputs - lists (required): an array of list definitions. each item contains: - name (required): the list's name (max 255 characters) - settings (required, nullable): filter, sort, and table column configuration. pass null for a list with no filters. - maximum 100 lists per call. ## output format confirm the created lists to the user, including each list's name and id.

Create multiple custom properties on the user's contacts database schema in a single operation. use this tool when you need to create several custom fields at once, for example when setting up form-to-contact mappings that require multiple new properties. ## what this tool does - creates multiple new custom properties in one call, available on all contacts. ## what this tool cannot do - create standard typeform contact properties (bio, company, job title, etc.). to activate disabled standard properties, use the enable_standard_contacts_database_properties tool instead. ## inputs - properties: an array of property definitions, each containing: - name: the name for the new property (must be unique). - type: the property type. the type is permanent and cannot be changed after creation. - long_text: general text (default) - email: email addresses - number: numeric values - phone_number: phone numbers - timestamp: date values - text_list: multiple choice options (configure with constraints) - constraints: optional. used with text_list to define choices and selection limits. - choices: array of {label, value} objects. - min_selected: minimum selections required. - max_selected: maximum selections allowed. set to 1 for single choice. ## output - the list of created properties.

Create or update multiple contacts in the user's contacts database in a single operation. use this tool when the user wants to add, create, update, or import several contacts at once. ## what this tool does - for each contact, if a contact with the same identifier (e.g. email) already exists, it updates that contact's properties. otherwise, it creates a new contact. - processes contacts in batches for efficiency. - deduplicates contacts within the same call by identifier, merging properties forward. ## inputs - contacts: an array of contact definitions, each containing: - properties: contact field values as property id and value pairs. - at least one identifying property (e.g. email) is required per contact. - maximum 1000 contacts per call. ## output - the list of created or updated contacts. each contact includes its id, identifier (value that uniquely identifies the contact) and an array of associated contact properties. ## property value formats when providing property values, use the following formats based on property type: - text (email, short_text, long_text, phone_number, code): {"type": "text", "text": "value"} - number: {"type": "number", "number": 42.0} - timestamp: {"type": "timestamp", "timestamp": "2024-01-15t00:00:00z"} - select (single_select, multi_select, text_list): {"type": "text_list", "text_list": ["option1"]}

Create a new contact in the user's contacts database. use this tool when the user wants to add, create, or register a new contact. ## what this tool does - creates a single contact with the provided properties. ## inputs - properties: contact field values as property id and value pairs. - at least one identifying property (e.g. email) is required. ## output - the created contact. includes its id, identifier (value that uniquely identifies the contact) and an array of associated contact properties. ## property value formats when providing property values, use the following formats based on property type: - text (email, short_text, long_text, phone_number, code): {"type": "text", "text": "value"} - number: {"type": "number", "number": 42.0} - timestamp: {"type": "timestamp", "timestamp": "2024-01-15t00:00:00z"} - select (single_select, multi_select, text_list): {"type": "text_list", "text_list": ["option1"]}

Create a new contacts list (segment) in the contacts database. ## use cases - create a new segment to organize contacts - create a list with custom filter and sort settings ## input - name (required): the name for the new contacts list (max 255 characters) - settings (required, nullable): filter, sort, and table column configuration. pass null for a list with no filters. ## output format confirm the created list to the user, including its name and id.

Create a form property mapping (sync config) to connect a form to contact properties. ## use cases - map form fields and variables to contact properties ## prerequisites before using this tool, call get_form_property_compatibility with the form_id to get: - available form fields and variables with their ids - compatible contact properties for each form field/variable - available choices for each field (in the choices array) ## mapping to subscription status when mapping a field to the subscription status property (template_id: "contacts.subscription_status"), you must include value_maps to translate form answers to subscription status values. ### for checkbox fields (choice-based — use choice_id): checkbox fields produce choice answers, not boolean. use source.type "choice_id" with the choice id from the field's choices array. a single-choice checkbox (e.g. marketing consent) maps the checked choice to "subscribed": value_maps: [ {source: {type: "choice_id", choice_id: ""}, target: {type: "text_list", text_list: ["subscribed"]}} ] ### for multiple_choice / picture_choice fields (choice-based — use choice_id): use source.type "choice_id" with the choice id from the field's choices array: value_maps: [ {source: {type: "choice_id", choice_id: ""}, target: {type: "text_list", text_list: ["subscribed"]}}, {source: {type: "choice_id", choice_id: ""}, target: {type: "text_list", text_list: ["never_subscribed"]}} ] ### for yes_no / legal fields (boolean answer type — use boolean): these are the only truly boolean fields. use source.type "boolean": value_maps: [ {source: {type: "boolean", boolean: true}, target: {type: "text_list", text_list: ["subscribed"]}}, {source: {type: "boolean", boolean: false}, target: {type: "text_list", text_list: ["never_subscribed"]}} ] ## output format present the created form property mapping to the user.

Delete a contact from the contacts database. ## prerequisites - call list_contacts first to find the contact id you want to delete. ## input - contact_id (required): the id of the contact to delete ## output format confirm the deletion was successful.

Delete multiple properties from the contacts database schema in a single operation. warning: this action is irreversible. either all properties are deleted successfully, or none are deleted (all-or-nothing). ## use cases - remove multiple properties that are no longer needed in one operation - clean up unused properties efficiently - batch deletion when reorganizing contact schema ## restrictions (same as single delete) - properties with prevent_delete: true cannot be deleted (e.g. subscription status) - the identifier property cannot be deleted (at least one identifier must remain) - all-or-nothing: if any property fails validation, no properties are deleted ## side effects (same as single delete) - lists/segments: deletion will fail if any list references any of these properties in its filters, sort orders, or visible columns — those lists must be updated first - contact data: existing values for deleted properties are not removed from contacts, but become inaccessible - form mappings: any form sync mappings targeting deleted properties will silently stop populating them - enrichment: enrichment configurations referencing deleted properties stop being applied ## input - property_ids (required): array of property ids to delete (use list_contacts_database_properties to find ids). must contain at least one property id. ## output format confirm all properties were successfully deleted with the count of deleted properties.

Delete a property from the contacts database schema. warning: this action is irreversible. ## use cases - remove a property that is no longer needed - clean up unused properties from the contacts schema ## restrictions - properties with prevent_delete: true cannot be deleted (e.g. subscription status) - the identifier property cannot be deleted ## side effects - lists/segments: deletion will fail if any list references this property in its filters, sort orders, or visible columns — those lists must be updated first - contact data: existing values for the deleted property are not removed from contacts, but become inaccessible - form mappings: any form sync mappings targeting this property will silently stop populating it - enrichment: enrichment configurations referencing this property stop being applied ## input - property_id (required): the id of the property to delete (use list_contacts_database_properties to find ids) ## output format confirm the deletion was successful.

Delete a contacts list (segment) from the contacts database. ## use cases - remove a segment that is no longer needed - clean up unused lists ## input - list_id (required): the id of the contacts list to delete ## output format confirm the deletion was successful.

Delete a form property mapping (sync config) by its id. ## use cases - remove form property mappings that are no longer needed ## input - sync_config_id (required): the id of the sync config to delete ## output format confirms the deletion was successful.