Jotform Apps

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_app, edit_app, search, fetch). 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.

mcp_app_request

Search apps. Use this tool when the goal is to find one or more apps that match optional title, date, and sorting filters. You can use this tool to find the app ID of an app by name or criteria to invoke any other tool that requires an app ID. This tool returns matching apps as search results and does not open or render a single app. Filter Rules: title_filter is an array of plain strings for app 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. Empty title_filter: Empty title_filter lists your apps. 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 apps are returned. Examples: (1) title_filter = ["dashboard"] to find apps with "dashboard" in the title; (2) title_filter = [] to list all your apps; (3) date_filter = ["2024-01-01", "2024-12-31"] to find apps created between January 1, 2024 and December 31, 2024; (4) order_by = "most_recent_created" to sort apps by the most recent creation date

search

Creates a complete app from a description: pages, elements, theme, and any embedded forms — all wired together in one call.

create_app

Edits an existing app using precise instructions. Can modify pages, elements, styling, settings, and app structure.

edit_app

This tool fetches information and metadata from Jotform based on an app id. If metadata.build_status is processing, wait metadata.poll_after_seconds and call fetch again with the same app id.

fetch

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

get_teams