Skip to main content
Free - like the rest of the MCP server, send_test_submission is not plan-gated.
Stores a test submission on a form so an agent can prove the form is live and receiving, without a human filling it in. The test row appears in the owner’s inbox with a Test badge. It is store-only: it sends no email, runs no spam scoring, and never counts toward the monthly quota. Each form keeps only its five newest test rows.

​
Input schema

​
Example call

​
Returned shape

​
What it does NOT do

  • No email is sent - not to the destination, not an autoresponder, nothing. This protects deliverability: an agent can never make Formpaste email a real or test address.
  • No spam scoring - the row is stored as received directly.
  • No quota impact - test rows never count toward your monthly submission limit.

​
Errors

A formId that doesn’t exist, or isn’t owned by the account behind the token, returns:
An empty fields object, or a payload over the field-count/size caps, returns invalid_input, too_many_fields, or field_too_large respectively. An invalid or revoked token returns the same auth error as every MCP tool - see MCP server.

get_form

Verify the form’s config alongside a test submission.

Cookbook prompts

Ready-to-use prompts that create, wire, and verify a form end to end.