nc-mcp-server

list_submissions

Read-onlyIdempotent

Retrieve form submissions (responses) by form ID, with optional full-text filtering and pagination. Returns submission details, questions, and filtered count for the form owner.

Instructions

List submissions (responses) to a form. Only the form owner can view submissions.

Args: form_id: Numeric form id. query: Optional full-text filter across answer text. limit: Max submissions to return (for pagination). offset: Starting offset (for pagination).

Returns: JSON object with fields: submissions (array of submission objects, each with id, userId, timestamp, answers), questions (the form's questions at submission time), filteredSubmissionsCount.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`offset`	No
`form_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish the operation is readonly, idempotent, and non-destructive. The description adds the owner-only access requirement and explains the return behavior with fields such as submissions, questions at submission time, and filteredSubmissionsCount. This goes beyond annotation coverage and gives practical behavioral context.

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

Conciseness5/5

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

The description is well-structured with a one-sentence purpose, a clearly labeled Args section, and a Returns section. Every line adds useful information and there is no filler or repetition of schema details.

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 readonly list operation, the description covers the required parameter, optional filters, pagination, and the exact shape of the returned data. Combined with annotations declaring safety, an agent has everything it needs to invoke the tool correctly without guessing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates. It names all four parameters: form_id, query, limit, and offset, and gives meaningful semantics such as full-text filter across answer text, pagination behavior, and the numeric nature of form_id. This is exactly what an agent needs beyond the bare schema titles.

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?

Description uses a specific verb and resource: 'List submissions (responses) to a form.' It clearly communicates a read-only listing operation. The scope is obvious and distinct from sibling tools like get_submission, even though alternatives are not explicitly named.

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

Usage Guidelines4/5

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

The description states a clear precondition: 'Only the form owner can view submissions.' This tells the agent when the tool is applicable. It does not explicitly compare with alternative tools like export_submissions or get_submission, but the core usage context is provided.

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

Deploy Server