Formify — AI Assisted E-Signing

Create Public Link

create_link

Destructive

Create a reusable public signing link from a PDF already uploaded with upload_file. The link is live the moment this returns — share the returned linkUrl yourself, Formify sends no invitations to anyone. THIS COSTS CREDITS. On the credits pricing model every live link is a billed instance, charged pro rata for the rest of the current period and renewed each period while it stays active. ALWAYS confirm with the user before calling this. Insufficient credits returns 402 and creates nothing; a suspended subscription returns 403. Requires the publicLinksCreate capability. signeeDetails here describes SIGNATURE SLOTS, not people: there are no recipients, so no email, phone, delivery method or signing order. signatureBox is required for every slot placed on an existing page, because there is no template to inherit coordinates from. BEFORE calling, ask the user: (1) the language signers should see, (2) whether the AI assistant should be enabled — only if get_account_capabilities confirms aiAssistant, (3) confirmation that a billed link may be created.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Name of the link. Shown in Formify, not to signers.
`fileId`	Yes	File ID from upload_file
`language`	No	Language of the signing experience shown to whoever opens the link (default en)
`aiAssistant`	No	Optional AI assistant that helps signees while reviewing the document. Requires the aiAssistant capability.
`signeeDetails`	Yes	The signature slots on the link. At least one is required.
`sharingSetting`	No	Who on the account may administer the link: private (default) or shared (requires the accessLevels capability). This does not affect who may SIGN it — a public link is public by definition.
`disablePrinting`	No	Prevent signers from printing the document.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 22, 2026

changedInput schema / properties / signeeDetails / items / properties / hidePersonalNumber / description

Previous value: -"Leave the signer's personal number out of the rendered signature. Only meaningful for signature types that collect one."New value: +"Leave the signer's national identity number off the rendered signature. Only meaningful for bankid_identification: the signer's BankID identification supplies that number to Formify's signing page, which prints it beside the signature by default. The number is handled by the signing page alone — it is never sent to, returned by or stored through this API."

changedInput schema / properties / signeeDetails / items / properties / idScanBox / description

Previous value: -"Required when signatureType is 'digital_ink_id_scan', unused otherwise."New value: +"Required when signatureType is 'digital_ink_id_scan', unused otherwise. The ID document itself is captured and read on Formify's signing page; only the placeholder's position is configured here, and no image or document data passes through this API."

changedInput schema / properties / signeeDetails / items / properties / paymentLink / description

Previous value: -"Collect a payment before this slot can be signed. Payment links are set up in the Formify client, not through this API — do not invent an id. The link must allow multiple use, since one public link is signed by many people. Requires the signAndPay capability."New value: +"Require a payment before this slot can be signed, by referencing a payment link that already exists on the account. Payment links are set up in the Formify client, not through this API — do not invent an id. The payment itself is taken on Formify's signing page: no card or payment data is collected, transmitted or stored by this API. The link must allow multiple use, since one public link is signed by many people. Requires the signAndPay capability."

changedInput schema / properties / signeeDetails / items / properties / signatureType / description

Previous value: -"Signature method for this slot. Same values and capability requirements as on a document: digital_ink (default), bankid_identification (signatureBankId), digital_ink_id_scan (signatureIdScan), face_liveness (signatureFaceLiveness). Call get_account_capabilities before using a non-default type."New value: +"Signature method for this slot. Same values and capability requirements as on a document: digital_ink (default), bankid_identification (signatureBankId), digital_ink_id_scan (signatureIdScan), face_liveness (signatureFaceLiveness). Call get_account_capabilities before using a non-default type. Identity verification for bankid_identification, digital_ink_id_scan and face_liveness is performed by Formify's signing page in the signer's browser, after the invitation is sent. This parameter only selects the method: no identity document, biometric data or national identity number is sent to, returned by or stored through this API."

AddedSep 16, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (readOnlyHint: false, destructiveHint: true), the description discloses the crediting/billing model, that the link is live immediately, that Formify sends no invitations, error behavior (402/403), and the requirement for a capability. This gives the agent essential knowledge beyond the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but information-dense, with critical warnings in ALL CAPS and a structured progression: purpose, immediate consequence, cost, prerequisites, then pre-call questions. There is minor redundancy between 'ALWAYS confirm with the user' and 'BEFORE calling, ask the user,' but the overall structure is effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex, costly, no-output-schema tool, the description is remarkably complete: it covers the input prerequisite (upload_file), capability checks, user-confirmation steps, credit costs, error codes, and even the output hint ('share the returned linkUrl yourself'). Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all parameters (100% coverage), so the baseline is 3. The description adds extra meaning by clarifying that signeeDetails describes signature slots, not people, and that signatureBox is required for existing-page placement because there is no template to inherit coordinates from. This goes beyond the schema, so a 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Create a reusable public signing link from a PDF already uploaded with upload_file.' It clearly distinguishes this from sibling create_* tools by emphasizing public, recipient-less, reusable links and the upload_file prerequisite.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit pre-call requirements: ALWAYS confirm with the user, ask about language, AI assistant (only if get_account_capabilities confirms aiAssistant), and confirmation of billing. It also states the capability requirement (publicLinksCreate) and clarifies when not to use this in recipient-based flows ('there are no recipients, so no email, phone, delivery method or signing order').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Formify — AI Assisted E-Signing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?