assignFieldsToSigners
ChatGPTAuto-detect fields in a sign document, create signer roles, and assign signature, date, and text fields to each signer. This tool handles both creating the signers and distributing the fields among them in one step.
bulkSendForSignature
ChatGPTSend a sign document to multiple recipients in bulk using an uploaded file (CSV or spreadsheet) containing recipient names and emails. Each recipient gets their own copy of the document to sign independently. Useful when the same document (e.g. an NDA or waiver) needs to be signed by many people.
createSignDocument
ChatGPTCreate a signable document that can be sent to one or more signers for e-signature. Use this tool when the user wants to collect signatures, build a signing workflow, or prepare a document for signing. The document content is generated from a text prompt; an optional uploaded PDF, image, or DOCX can be passed as reference context (it is analyzed, not used as the final file).
createSigningLink
ChatGPTGenerate a shareable signing link for a document instead of emailing signers directly. Useful when the user wants to share the signing URL manually via chat, SMS, or other channels.
create_sign_document
ChatGPTCreate a signable document that can be sent to one or more signers for e-signature. Use this tool when the user wants to collect signatures, build a signing workflow, or prepare a document for signing. The document content is generated from a text prompt; an optional uploaded PDF, image, or DOCX can be passed as reference context (it is analyzed, not used as the final file).
displaySignDocument
ChatGPTRefresh and display an already-created signable document in the rendered App. Returns the document with fresh, time-limited file URLs so it can be previewed again after the previous URLs expire. Requires the document_id and form_id of an existing sign document.
display_sign_document
ChatGPTRefresh an already-created signable document in the rendered App so it can be previewed again after its previous preview expires. The refreshed document is handed to the App, which renders it; the response reports which document was refreshed. Requires the document_id and form_id of an existing sign document.
downloadSignedDocument
ChatGPTReturn the completed, sealed PDF of a fully signed document including the audit trail. Only available once all signers have completed signing.
editSignDocument
ChatGPTEdit an existing sign document. Can update the document title, regenerate the document content from a new prompt, or modify document settings.
edit_sign_document
ChatGPTEdit an existing sign document. Can update the document title, regenerate the document content from a new prompt, or modify document settings.
getSigners
ChatGPTRetrieve the list of signers (participants) on a sign document, including their participant IDs, names, emails, roles, and assigned fields. Use this to get participant IDs before updating signers.
getSigningStatus
ChatGPTReport the current status of a sign document including overall document status and per-signer status (sent, viewed, signed) with key audit events and timestamps.
get_signers
ChatGPTRetrieve the signers of a sign document or sign form — participants that have signature/date/text fields assigned to them — including their participant IDs, names, emails, roles, signing order, and signing status. When given a form ID, this returns signers across all of the form's documents (the editable draft plus every sent document), each annotated with its document ID and status. Participant roles with no assigned fields are excluded. Use this to see who has been sent a document and to get participant IDs before updating signers.
get_signing_links
ChatGPTGet the signing links for a sent Jotform Sign document that is waiting for the current account's signature. Use when the user wants to sign a document sent to their account email. Returns one link per role the user can sign now, in signing order; with signing order enabled, later roles appear only once it is their turn. Share every link: each role is signed separately in the browser. Signing does not happen in chat. Does not sign or change the document.
get_signing_status
ChatGPTReport the current status of a sign document including the overall document status and per-signer status (sent, viewed, signed, declined) with key timestamps. Accepts a sign document ID or a sign form ID (as seen in the /sign/{id} builder URL); A sent document ID reports that copy only. A form ID or draft document ID aggregates all non-deleted sent copies, or reports the draft if no copies have been sent. Performs a single status lookup.
get_teams
ChatGPTRetrieves team information for the user in Enterprise environments. Returns team details including members when returnBasicTeamInfo is false.
listSignDocuments
ChatGPTList the user's sign documents with their current statuses. Supports filtering by status. Use this to help the user find or manage their documents.
listSubmissions
ChatGPTList signatures and signing submissions for sign documents. Use this tool when the user wants to view who has signed, check signatures, or see signing activity. You can list submissions for a specific sign document by passing its form_id, or across all sign documents when form_ids is empty.
list_submissions
ChatGPTList signatures and signing submissions for sign documents. Use this tool when the user wants to view who has signed, check signatures, or see signing activity. You can list submissions for a specific sign document by passing its form_id, or across all sign documents when form_ids is empty. Do NOT use this tool to list the user's sign documents themselves — use the sign document listing/search tool for that.
mcp_app_request
ChatGPTMakes an authenticated request to the Jotform REST API with the given method, body, and query parameters. The API host is resolved automatically for the current account, so pass only a relative path. WHEN TO USE: Prefer a dedicated tool when one exists for the requested action (for example: create_form, edit_form, list_submissions, search, fetch, display_form, analyze_submissions). Only use this tool as a fallback when no dedicated tool covers the request. See https://api.jotform.com/docs/ for the full API reference. COMMON ENDPOINTS (relative paths, grouped by resource; not exhaustive): - User: "user", "user/forms", "user/submissions", "user/folders", "user/reports", "user/settings", "user/usage". - Form: "form/{formID}", "form/{formID}/questions", "form/{formID}/question/{questionID}", "form/{formID}/properties", "form/{formID}/properties/{propertyKey}", "form/{formID}/submissions", "form/{formID}/files", "form/{formID}/reports", "form/{formID}/webhooks". - Submission: "submission/{submissionID}". - Report: "report/{reportID}". - Folder: "folder/{folderID}". RULES: - Use a relative path with no leading slash and no "API/" prefix (use "user", not "/API/user" or "/user"). - The endpoints above are examples, not a complete list. You may use any documented Jotform API endpoint. Do not invent sub-resources; if unsure, start from a parent/collection endpoint above (for example "form/{formID}/properties") instead of guessing a new path. - "emails", "conditions", "products" and "formStrings" are not standalone endpoints and are not valid {propertyKey} values. They are returned as grouped sections of "form/{formID}/properties", so read them from there. - Treat a 404 as "this path does not exist" and report it, instead of retrying variations of the same path. TIP: To reference a specific question or property, first GET the parent collection ("form/{formID}/questions" or "form/{formID}/properties") and use the IDs/keys returned there instead of guessing.
search
ChatGPTSearch and list the user's Jotform products of these types only: sign document. Use this tool to find products by name or criteria, to list products of one or more types, or to get a product ID for another tool. It does not search submissions. product_type: array of types to include; ["ALL"] covers every available type (sign). filter.title_filter: array of plain strings matched against product titles (OR logic, no regex). Matching is per whole word and case-insensitive, with no partial or plural matching: "invoice" does not match the title "Invoices 2024", so pass every spelling you want covered as its own array element, e.g. ["invoice", "invoices", "billing"]. A multi-word element needs most of its words present in the title, so prefer separate single-word elements to widen a search. Empty array lists all products of the requested types. filter.date_filter: [start, end] creation-date range in YYYY-MM-DD format, or empty array for no date filter. filter.status_filter: null lists active products. favorited_only lists owned favorited products; archived_only lists owned archived products; trashed_only lists owned trashed products. filter.is_filtered_by_rules: LAST RESORT (extra AI call) — only when no title keyword can express the criteria, such as the language a title is written in or an abstract topic with no obvious keyword. When the request contains a plausible title word, ALWAYS prefer filter.title_filter, listing several keyword variants (synonyms, singular and plural, translations) in one call rather than setting this true. If both are sent, the keywords are applied first and the AI pass runs only when they match nothing, so it cannot refine keyword matches further. Never present unfiltered results for criteria the filters could not express. Enterprise server admins: active-status searches cover ALL assets on the server (with owner and team info, server-wide totals and workflow error counts); owned-state filters stay scoped to the admin's own products. order_by: default "last_activity"; only use another option when the user asks for a specific sorting. Examples: (1) product_type=["ALL"], filter.title_filter=["invoice", "invoices"] to find products whose title contains either word; (2) product_type=["sign"] to list products of one type; (3) filter.status_filter="trashed_only" to list trashed products.
sendForSignature
ChatGPTSend a sign document to all assigned signers via email. Supports signing order, auto-reminders, and expiration settings. This action emails real people — confirm with the user before calling.
sendSignReminder
ChatGPTSend a reminder email to pending signers who have not yet signed the document.
send_feedback
ChatGPTReport unsupported user requests and missing capabilities in the current Jotform app to the Jotform team. Primary use: when the user requests an action that the available tools cannot perform, call this tool with category=missing_capability before explaining the limitation. The user does not need to ask for feedback or request a report. First establish the gap from the available tool descriptions or an explicit unsupported-operation result. Do not report missing input, authentication failures, permission restrictions, temporary errors, or an operation that the available tools can perform as missing capabilities. Also use when the user explicitly wants to submit a bug report, suggestion, or general feedback. Send only a brief, generic summary of the unsupported action or feedback, without personal data, credentials, document contents, submission data, or chat transcripts. Follow the host data-sharing permissions and confirmation requirements. After the call, explain the limitation and continue with any supported parts of the task. Only say feedback was recorded if the result confirms success. This records feedback; it does not perform the unsupported action, open a support ticket, or promise implementation.
send_for_signature
ChatGPTSend a sign document to signers via email. A sign document has a fixed set of signer roles (signature slots). Each send dispatches one independent copy of the document to one person per role — a "set". The number of signer roles only controls how many people are on a single copy; it is NOT a limit on how many people can ever receive the document. You can call this tool as many times as needed to send additional independent copies to different people: a one-signer document can be sent to any number of individuals (one copy each), and a multi-signer document can be sent to different sets of people (one copy per set). To send a copy to a different person or set of people, first point the signer role(s) at them with the updateSigner tool (set each role's name and email), then call this tool — there is no separate "add signer" step, and having only one signer role does not prevent sending to more people. Supports signing order and auto-reminders. This action emails real people — confirm with the user before calling.
sign_home
ChatGPTOpen the Jotform Sign home.
sign_in
ChatGPTConnect a Jotform account. Use it when the user wants to sign in, use their existing Jotform account or see the documents in it, or when a result says the session has no Jotform account. Signing in keeps the drafts made before it.
updateSigner
ChatGPTUpdate an existing signer on a sign document with their name, email, and optional signing order. Use this to fill in signer details (e.g. after assignFieldsToSigners created the signer roles). Call this tool once per signer that needs updating.
update_sign_document_content
ChatGPTSaves user-edited HTML content of an AI-created sign document and regenerates its PDF and fields.
update_signer
ChatGPTUpdate an existing signer role on a sign document with a person's name, email, and optional signing order. Use this to fill in signer details (e.g. after assignFieldsToSigners created the signer roles), or to re-target a signer role to a different person before (re-)sending: update the role's name and email here, then call sendForSignature again to send a new independent copy to that person. A document keeps the same signer roles across sends, so repeating updateSigner + sendForSignature lets you send copies to any number of different people even when there is only one signer role. Get valid participant IDs from getSigners. Call this tool once per signer role that needs updating.
createSignDocument
Claudecreate_sign_document
ClaudedisplaySignDocument
Claudedisplay_sign_document
ClaudeeditSignDocument
Claudeedit_sign_document
ClaudegetSigners
ClaudegetSigningStatus
Claudeget_signers
Claudeget_signing_status
ClaudelistSignDocuments
ClaudelistSubmissions
Claudelist_submissions
Claudemcp_app_request
Claudesearch
ClaudesendForSignature
Claudesend_for_signature
ClaudeupdateSigner
Claudeupdate_sign_document_content
Claudeupdate_signer
Claude