Backforms MCP

get_form_submissions

Retrieve recent leads, contact inquiries, and submissions for a specific Backforms form endpoint by form_id, with optional filtering by spam status and result limit.

Instructions

Retrieves recent leads, contact inquiries, and submission entries received by a specific form endpoint.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "form_id": "<form_id>"
    },
    "name": "get_form_submissions"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of submissions to retrieve (default: 10, max: 50)
`status`	No	Filter submissions by spam status (default: 'all')
`form_id`	Yes	UUID of the form endpoint in Backforms

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Oct 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it says little beyond 'Retrieves'. It does not disclose ordering, pagination, whether spam is included by default, authentication requirements, or what a result entry looks like. 'Recent' is the sole behavioral hint and is vague.

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?

A single front-loaded sentence with no filler or repetition of the tool name. The enumerated list ('leads, contact inquiries, and submission entries') is slightly redundant, keeping it just short of ideal.

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

Completeness3/5

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

For a simple read tool with 100% schema coverage, the description covers the essential purpose and hints at return content. However, with no output schema and no annotations, it should say more about the returned shape, ordering, and pagination than it does, leaving gaps for an agent calling it.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters (limit, status, form_id) are already documented in the schema, establishing a baseline of 3. The description adds only that submissions are 'recent' and consist of leads/contact inquiries, which is marginal semantic value over the schema.

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

Purpose4/5

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

The description states a specific verb ('Retrieves') and resource ('leads, contact inquiries, and submission entries received by a specific form endpoint'), making clear this is a read of form submissions. It does not explicitly contrast itself with siblings like get_form_details, but no sibling plausibly overlaps, so an agent can still select it confidently.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, no prerequisites (e.g. needing a valid form_id from list_forms), and no exclusions. The only hint is the word 'recent', which implies a recency-oriented listing but is not framed as usage guidance.

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

Deploy Server