Skip to main content
Glama

List submissions

list_submissions
Read-onlyIdempotent

Submissions of one form, newest first. Search in this order: read a page of recent submissions to see the field names people are sending now, widen that list with get_form_fields when you need more names, use q for a first pass when you do not know which field holds the text, then narrow with field filters. When you do not know how many submissions an answer covers, call count_submissions before paging through them, and when you do not know what values a field holds, call it with group_by field: and select the ones you want with a field in filter. Filters combine with AND: q, status (inbox, spam, all), read, has_attachments, created_after, created_before, country, and up to 5 field filters (eq, contains, starts_with, exists, in). Pass fields to return only the values you need when you are scanning many submissions. Follow next_cursor until it is null. Not possible here, so say so rather than approximating: no totals in this tool, no "not equal" or "does not contain", no greater than or less than on a value, and no sorting by anything but time. To compare numbers, filter to the submissions that have the field, pass fields to read just that value, and compare them yourself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAny field contains this text, matched literally and without case. Use it first when you do not know which field holds the text. On some forms it covers only the fields recent submissions carry, so reach an older field by name with a field filter.
readNoOnly read (true) or unread (false) submissions.
fieldNoUp to 5 filters keyed by field name, spelled the way the submissions spell it. Each is an object with one of eq, contains, starts_with, exists or in. Several filters combine with AND. Example: {"email": {"contains": "@example.com"}, "plan": {"in": ["pro", "team"]}}.
limitNoSubmissions per page. Keep it small.
orderNoNewest first (default) or oldest first.newest
cursorNo
fieldsNoOnly return these submitted fields, separated by commas, such as "email,name". Use it when you are scanning many submissions for one or two values, so the rest does not come back.
statusNoinbox
countryNoTwo-letter uppercase country code. For several, separate them with commas, such as "DE,AT,CH". Max 20.
form_idYesForm id, a short string such as "AbC123xyz" (from list_forms).
created_afterNoRFC 3339 date or time, inclusive.
created_beforeNoRFC 3339 date or time, exclusive.
has_attachmentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses pagination via next_cursor, the AND-combination of filters, the absence of totals, and unsupported operations like 'not equal'. This gives the agent a full picture of the tool's 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?

The description is long but information-dense; every sentence adds operational guidance. It is front-loaded with the core purpose and then proceeds logically through workflow, filters, and limitations. While not terse, the length is justified by the tool's complexity.

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?

Given 13 parameters, nested filter objects, and no output schema, the description covers pagination, filter composition, limitations, and fallback strategies. It also instructs the agent to state when a requested operation is not possible. Nothing critical for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is high (77%), so the description need not re-explain each parameter. However, it adds crucial cross-parameter semantics: how filters combine with AND, the recommended search order, and the use of 'fields' to limit payload. This exceeds the baseline for high schema coverage.

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?

The description states clearly that this lists submissions for one form, newest first, and distinguishes itself from other search tools by providing a specific search order. It also explicitly lists what this tool cannot do, preventing misuse.

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

Usage Guidelines5/5

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

It provides a concrete workflow: start with a page of recent submissions, widen with get_form_fields, use q for unknown fields, then narrow with field filters. It also references count_submissions and get_form_fields for specific scenarios and tells the agent when to say something is not possible rather than approximating.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources