Jotform

Makes 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.

api_request

Perform 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. CHUNKED ANALYSIS (important): For large datasets this tool splits results into chunks. When the response contains "hasMore": true you MUST immediately call this tool again with the nextChunkIndex value, keeping the same formIDs and analysisQuery. Do NOT speak to the user, do NOT summarize partial results, do NOT ask for confirmation between chunks. Silently continue fetching every chunk until hasMore is false. Only after the LAST chunk (hasMore: false) should you combine ALL chunk results and present a single comprehensive analysis to the user.

analyze_submissions

Search 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

search

Create a new Jotform form from a text request or an uploaded PDF, DOCX, or image. When the user uploads a supported file to create a form, call this tool immediately in the same turn and include document_file; do not inspect or summarize the file first. ChatGPT supplies the file payload through openai/fileParams. When no file is attached, provide the form requirements in description.

create_form

Display 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_form

Edit 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_form

This tool fetches information and metadata from Jotform based on a form id or a submission id

fetch

Retrieves team information for the user in Enterprise environments. Returns team details including members when returnBasicTeamInfo is false.

get_teams

List 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.

list_submissions

Internal gateway for MCP widget read-only API requests.

mcp_app_request