analyze_submissions
ChatGPTPerform deep AI-powered analysis on one or more forms' submissions. Use this tool when the user wants insights, patterns, statistics, trends, or summaries derived from submission data. This tool requires formIDs—use search_asset first if you need to find the form IDs. Supports analyzing multiple forms in parallel; results are combined into a single response. Examples: "What are the most common responses?", "Show trends in submission dates", "Analyze sentiment in feedback", "Give me a statistical summary". Do NOT use this tool for simply listing or browsing submissions—use list_submissions instead.
api_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.
create_app
ChatGPTCreates a complete app from a description: pages, elements, theme, and any embedded forms — all wired together in one call.
create_form
ChatGPTCreate a new form based on the user's prompt
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).
create_submission
ChatGPTCreate a submission for a form.
display_app
ChatGPTDisplay an existing app when the user wants to see, show, open, or view a specific app. Used for displaying a single app. If the user wants to list or search apps, use the search tool instead. Requires a known app ID. If the app ID is not known yet, use search first. Example scenario -- "Show me my event app": First step: Use the search tool to find the app ID of the event app. Second step: Use the display app tool with the app ID to display the app. --
display_form
ChatGPTDisplay an existing form when the user wants to see, show, open, or view a specific form. Used for displaying a single form, if the user wants to list or search forms, use search tool instead. Requires a known form ID. If the form ID is not known yet, use search first. Example scenario -- "Show me my quiz form": First step: Use search tool to find the form ID of the quiz form. Second step: Use display form tool with the form ID to display the form. --
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.
download_app_mobile_export
ChatGPTGenerate an Android or iOS source project ZIP from the current app settings and return it as an authenticated binary resource, up to 10 MiB, with filename, byte size and SHA-256. The resource URI is an identifier, not a download URL. Use search to resolve an unknown app ID and ask for the platform if unspecified. This does not build, install, sign or publish the app. If the client can save binary resources, use its native file handling or transfer the raw bytes directly through an available tool execution runtime; never transcribe base64 through model output. Verify the saved file against the returned size and SHA-256, then extract into a new directory and read README.md and AGENTS.md. If the tool succeeds but the client reports unsupported ZIP resources or cannot save the file, explain that the project was generated but could not be saved in this environment. Give these manual download steps: open the app in App Builder, select Publish > Mobile App, and choose the requested Android or iOS download. Only claim a download succeeded after a file was actually saved. The returned SHA-256 identifies this resource only; a separate browser download generates a new ZIP and may have a different checksum.
edit_app
ChatGPTEdits an existing app using precise instructions. Can add, modify, or remove pages and elements, and change styling, settings, and app structure. Changes may remove existing content or overwrite existing settings.
edit_form
ChatGPTEdit a form based on the user's prompt. Use high-level natural-language instructions only (e.g., "Add a name question at the top", "Move the email question to the end"). Do not specify internal field types, control names, or IDs. Another agent will map your intent to exact field types.
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.
fetch
ChatGPTThis tool is fetching information and metadata from the Jotform based on a form id or a submission id
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.
jotform_home
ChatGPTOpen the Jotform home.
list_sign_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.
list_submissions
ChatGPTList or filter form submissions. Use this tool when the user wants to view or filter submissions of forms. You can list or filter submissions of a single form or multiple forms by passing the form_ids. When form_ids is empty, submissions are listed across the user's most recent forms, ordered by unread submissions. If the user's query contains any form name, partial name, or keyword that identifies a form (e.g. "Student Information Form", "RSVP", "Contact"), you must resolve those to numeric form IDs before calling this tool. Filter Rules: date_filter is an array of two strings for the date range to filter by. The first item is the start date and the second item is the end date. Return empty array if no date filter is needed. Filter Rules: is_filtered_by_rules is a boolean to indicate if the submissions are filtered by rules. Do NOT use this tool for analysis, summaries, patterns, or statistics—use analyze_submissions instead.
search
ChatGPTSearch assets. Use this tool when the goal is to find one or more assets that match optional title, date, submission-count, and sorting filters. You can use this tool to find the asset ID of a asset by name or criteria to invoke any other tool that requires a asset ID. This tool returns matching assets as search results and does not open or render a single asset. Submissions are not a asset type. This tool does not search submissions. Filter Rules: title_filter is an array of plain strings for asset title matching (OR logic). Regex is not supported. Filter Rules: date_filter is an array of two strings in YYYY-MM-DD format for the date range to filter by. The first item is the start date and the second item is the end date. Return empty array if no date filter is needed. Filter Rules: min_submission_count is for the minimum number of submissions to filter by. Return zero if no submission filter is needed. Return 1 if the user wants to assets which have submissions. Empty title_filter: Empty title_filter lists your assets. order_by: The default value is "last_activity", only use another option if a specific sorting is provided by the user. Limit controls how many assets are returned. Examples: (1) title_filter = ["invoice"] to find assets with "invoice" in the title; (2) title_filter = [] to list all your assets; (3) date_filter = ["2024-01-01", "2024-12-31"] to find assets created between January 1, 2024 and December 31, 2024; (4) order_by = "most_recent_created" to sort assets by the most recent creation date
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_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.
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.
analyze_submissions
Claudeapi_request
Claudeassign_form
Claudecreate_app
Claudecreate_form
Claudecreate_sign_document
Claudecreate_submission
Claudedisplay_form
Claudedisplay_sign_document
Claudeedit_app
Claudeedit_form
Claudeedit_sign_document
Claudefetch
Claudeform_list
Claudeget_embed_code
Claudeget_signers
Claudeget_signing_links
Claudeget_signing_status
Claudeget_submissions
Claudeget_teams
Claudelist_sign_submissions
Claudelist_submissions
Claudesearch
Claudesend_for_signature
Claudeupdate_sign_document_content
Claudeupdate_signer
Claude