Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List form submissions

list_form_submissions
Read-only

List form submissions filtered by form or status with pagination, returning each submission's data and status for triage of pending, processed, spam, or archived entries.

Instructions

List form submissions, optionally filtered by form and status; paginated. Returns submission rows with their data and status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_form_submissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
limitNo
statusNoOptional status filter
formIdOrSlugNoOptional form id or slug to filter submissions by

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.146.2
    • changedInput schema / properties / skip / minimum
      Previous value: --9007199254740991New value: +0
  2. Changed3 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / limit / default
      Removed value: -50
    • removedInput schema / properties / skip / default
      Removed value: -0
  3. First observedv0.73.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that results are paginated and that rows include their data and status, which is genuinely useful given there is no output schema, but it omits defaults, page size limits, and ordering behavior.

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 compact sentence that front-loads the action, then filters, then pagination, then return shape. No filler, though the return-shape clause could be trimmed if an output schema existed.

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?

With no output schema, the description responsibly states what comes back ('submission rows with their data and status'). However, for a paginated list tool with two undocumented paging parameters, an agent still lacks default page size, maximum limit, and result ordering.

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 coverage is only 50%, with skip and limit carrying no descriptions at all; the description's 'paginated' gesture toward them does not explain offset/limit semantics or why limit permits negative values. It does correctly map 'filtered by form and status' onto formIdOrSlug and status, matching the enum provided in 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 opens with a specific verb+resource ('List form submissions') and immediately scopes it with the optional filters and pagination. It is clearly distinguishable from the singular 'get_form_submission' by the plural list framing, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

'optionally filtered by form and status; paginated' implies the retrieval use case, but there is no statement of when to reach for this versus get_form_submission or the other list_* tools, and no exclusions or prerequisites.

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

Deploy Server

Other Tools