Tool reference
The nineteen tools FormMaker gives your AI client, and when each one earns its keep.
Once FormMaker is connected, your client sees nineteen tools. You don't call them yourself — you ask for what you want and the model picks. These pages are for when you want to know exactly what it picked, and what it sent.
Every parameter table here is generated from the tool definitions the server actually registers, so it can't quietly drift out of date.
Finding and reading forms
list_forms
Every form in the portal, with field counts.
get_form
One form's full definition.
audit_form
The graded CRO report.
Cleaning up the portal
audit_submissions
Which recent submissions are junk, and why.
find_duplicate_forms
Redundant forms, and which copy to keep.
Writing to something other than a contact
list_object_types
The custom objects your portal defines.
list_object_properties
What one custom object can hold.
create_object_form
Define a form that writes to a custom object.
generate_object_form
A Generation Brief for that form.
Rebuilding forms as code
list_form_targets
The frameworks it can build for.
generate_form
A Generation Brief for one form.
extract_brand
Colors and type from your site.
Hosting a form
create_hosted_form
A form FormMaker renders and hosts, for an embed or a link.
update_hosted_form
Change a hosted form's title, button, theme, or mode after creating it.
list_form_templates
Ready-made field sets to start a hosted form from.
Nothing here writes to HubSpot
An audit can't change your form, and a generated form is code handed back to you, not something published to your portal.
create_object_form, create_hosted_form, and update_hosted_form are the only ones that write
anything at all, and what they write is a form definition FormMaker owns — not a change to your CRM.
Your records are only ever touched by a real submission to a form you built, from your own site.