Skip to main content
Glama

Checkout Page

by com.checkoutpage
OverviewDiscussionsAdmin

list_submissions

Read-only

Retrieve a paginated list of form submissions processed through your Checkout Page account. Pass livemode: false to read test-mode records.

This tool is useful for customer-support and operations questions about what a person submitted on a form, which page a submission came from, and when it was captured.

Example uses:

  • "Show me recent submissions"

  • "Find submissions from jane@example.com"

  • "Find submissions for customer 6812fe6e9f39b6760576f01c"

  • "Show submissions for form X"

  • "Show submissions for the Lead Capture Form"

  • "Show failed submissions"

  • "How many submissions did I get this week?" — apply a date range and read total

Example support uses:

  • Customer says they filled in a form but is unsure it went through — search by email and check whether a matching submission exists and whether status is succeeded or failed.

  • Merchant wants all submissions for a specific person — use search with email or name, or customerId when known.

  • Merchant wants submissions from a specific form — use pageId when you know the page ID, or search with the form title.

  • Merchant wants the full payload for one result — first call list_submissions, then pass a returned id into get_submission.

Data limitations:

  • No tool in the MCP can edit or delete submissions.

  • Submission records show what was captured, but not downstream fulfillment or email delivery status.

Date filters: Always use UTC timestamps with the Z suffix (e.g. 2026-03-01T00:00:00Z). Never use local timezone offsets — dates are stored and compared in UTC.

Submissions are returned sorted newest-first. Use cursor-based pagination (starting_after / ending_before) to page through large result sets. starting_after and ending_before cannot be used simultaneously. Max limit is 100, default is 10.

This tool is read-only. You cannot modify or delete submissions through MCP. For those actions, explain what is on file and direct the merchant to the Checkout Page dashboard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of records per page (integer, max 100, default 10).
pageIdNoFilter by the form page ID that received the submission.
searchNoSearch by `customerEmail`, `customerName`, and `formTitle`. Contains match (for example, 'jane' matches 'jane@example.com' and 'Jane Smith', while 'lead' matches 'Lead Capture Form').
statusNoFilter by submission status. Valid values: succeeded, failed.
livemodeNoSet to false to read test-mode records (created while a page was in test mode). Defaults to live records.
customerIdNoFilter by the associated customer ID.
createdAfterNoFilter by lower bound of createdAt. Use a UTC ISO 8601 timestamp with a `Z` suffix.
createdBeforeNoFilter by upper bound of createdAt. Use a UTC ISO 8601 timestamp with a `Z` suffix.
ending_beforeNoCursor-based pagination. Pass a record `id` to return results before it. Cannot be used with `starting_after`.
starting_afterNoCursor-based pagination. Pass a record `id` to return results after it. Cannot be used with `ending_before`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
totalYesTotal number of records matching the query across all pages.
has_moreYesWhether more records exist beyond the current page.

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?

Annotations declare readOnlyHint/destructiveHint, but the description adds substantial context beyond them: no tool can edit/delete submissions, records omit downstream fulfillment and email-delivery status, results are newest-first, pagination cursors are mutually exclusive, limit caps at 100/default 10, and date filters must be UTC with Z.

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?

Front-loads purpose, then sections for examples, support uses, data limitations, dates, and pagination. Well organized and skimmable, though the read-only point is stated twice ('This tool is read-only' and 'You cannot modify or delete submissions') and the example list is long.

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?

With an output schema present, return values need not be detailed, and the description still references relevant fields (`total`, `status`, `id`). For a 10-param read-only list tool, all decision-relevant context is present.

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 100%, so baseline is 3, but the description adds genuine selection meaning beyond the schema: it explains when to prefer pageId vs search vs customerId, that a date range plus `total` answers count questions, and reiterates the UTC-only date constraint.

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?

Opens with a specific verb+resource+scope: 'Retrieve a paginated list of form submissions processed through your Checkout Page account.' It also distinguishes itself from the sibling get_submission by naming it for the single-record case.

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?

Provides explicit routing guidance (use pageId when you know the page ID, search with the title otherwise; follow up with get_submission for full payload) plus concrete example queries and support scenarios. When-to-use is unambiguous.

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

All Checkout Page 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