PlatoForms

Queue a new PlatoForms web form from a natural-language description (30-1000 characters describing the form's purpose and fields). style 'classic' shows all fields on one page; 'conversational' asks one question at a time; the user re-confirms this choice in the builder. IMPORTANT — this tool only saves the prompt and hands back a link. It does NOT generate the form. The form is designed in the builder, where the user answers a few clarifying questions, picks the form style, and ticks the final field list before anything is created. So: - Say the form is READY TO BUILD and the design starts when they open the link — never say the form is created, generated or finished. - Do NOT list, name or count the fields. You do not know them; the builder's own AI decides them and the user edits that list. Listing a guessed field list misleads the user. - Do NOT call get_form_fields; it would return an empty form. - There is NO update/edit API for these forms. Do not offer to tweak, add or remove fields afterwards — further changes are made by the user in the builder, or by creating another new form.

Create a new PDF document (jarvis-doc) from a natural-language description (30-1000 characters describing the document's content and layout) — e.g. an invoice, contract, or intake packet. IMPORTANT — this tool only saves the prompt and hands back a link. It does NOT generate the document. Opening edit_url starts the document editor's AI agent on that prompt, and the agent designs it there. So: - Say the document is READY TO BUILD and the design starts when they open the link — never say it is created, generated or finished. - Do NOT describe the sections, pages or content as if they exist. You have not seen the result; the editor's agent decides it. - There is NO update/edit API for these documents. Do not offer to change it afterwards — the user keeps refining it by talking to the AI agent inside the document editor, or asks for a new document.

Create shareable form link(s) with fields pre-filled — e.g. "send Sarah a link with her email already filled in". `name` labels the invitation in the PlatoForms review UI (required so the team can audit it). `prefill_values` is keyed by field id from get_form_fields, same encoding as submit_form. Prefilled fields are read-only for the recipient unless prefill_editable=true. number_of_links (1-10) creates that many distinct tracked links. expires_at (ISO datetime) closes the form for these links after that time. Returns the link URLs — share them with recipients yourself; this tool never sends email.

Find submissions of a form where a specific field exactly matches a value — e.g. find the submission where the email field is '[email protected]'. field_id is the field's id (fid...) from get_form_fields. Matching is exact (not substring).

Create a time-limited public download URL for a submission file. kind='pdf' needs pdf_id when the submission lists multiple PDFs (use the template_id/id values from get_submission; defaults to the form's main PDF). kind='attachment' requires attachment_id from get_submission. expires_in accepts '30m', '2h', '7d'; omit to use the form's configured expiry. Share the returned URL instead of downloading file bytes.

Get a form's field schema: every field's id (fid...), type, label, required flag, options, and validation rules. Call this before submitting to a form or interpreting submission values. Set draft=true for the unpublished draft version of the form.

Get one submission in full: every submitted field value (with field labels), submitter info, and the inventory of generated files. Use get_download_link to obtain URLs for those files.

List the user's PlatoForms forms (id, name, folder, publish state, submission count). Returns at most 200 forms; if truncated, use search_forms with a keyword to find a specific form instead.

List the team's PDF documents (jarvis-docs, newest first): id, name, page count, and edit URL. These are standalone PDF documents, separate from the fillable forms returned by list_forms.

List submissions of a form (newest first): submission id, date, submitter, and available files (PDFs, attachments). Use get_submission for the submitted field values. Date filters accept ISO dates or datetimes, e.g. submitted_after='2026-08-01' or '2026-08-01T12:00:00Z'.