Skip to main content
Glama

Formstep

by io.github.formstep
OverviewDiscussionsAdmin

List submissions

formSubmission_list
Read-only

List submissions for a form (paginated). Read-only. Call form_list for formId first. Each item carries answers keyed by field key — a choice is its option key, a matrix { row_key: column_key }, a repeating group [{ member_key: value }] — and display, the same keys as readable text. This is the shape request_get and every webhook or callback use; call fields_list for the keys' titles and option labels. translationLanguage optionally attaches a stored AI translation under item.translation.display (same keys); item.answers and item.display always stay the original. Drafts (isCompleted false) come back by default on Pro and Business; on Free only completed submissions are listed. Returns { formId, formName, items, nextCursor, hasMore, canPaginate } — canPaginate is true only when another page is fetchable via nextCursor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size (1–100, default 20).
cursorNoOpaque cursor from a prior response's `nextCursor`. Omit to start at page 1.
formIdYes
includeDraftsNo
translationLanguageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare read-only, but the description adds substantial context beyond them: draft visibility differs by plan (Pro/Business default on, Free completed only), translation attachment behavior, and the full return-shape including canPaginate/nextCursor semantics.

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

Conciseness3/5

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

Front-loads purpose and pagination well, but packs answer-shape details, translation behavior, plan-based drafts, and return-shape into a dense run-on. Information-dense and useful, yet not tightly structured.

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?

No output schema, so spelling out { formId, formName, items, nextCursor, hasMore, canPaginate } and canPaginate's meaning is essential and complete, alongside draft/translation and shape semantics.

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 coverage is only 40%, so the description compensates heavily: it explains translationLanguage's effect on item.translation.display vs original answers, the includeDrafts/isCompleted distinction, and cursor/nextCursor pagination flow.

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?

States a specific verb+resource ('List submissions for a form') and immediately differentiates from siblings by naming form_list, request_get, and fields_list as related but distinct calls.

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?

Provides a clear prerequisite ('Call form_list for formId first') and points to fields_list for keys' titles/labels. Does not cover when to prefer request_list/formAnalytics_get for other querying needs.

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

All Formstep toolsInspect
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