Skip to main content
Glama
hybriden

Paperboy CMS

Official
by hybriden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_form_submissions

Read-only

Retrieve form submissions from a Paperboy CMS site, ordered by date descending, with paging and original field labels preserved. Requires submission.read.

Instructions

List form submissions in this site, newest first, one page at a time. Answers come with a snapshot of the field labels as they were when submitted, so a later edit to the form does not rewrite history. Visitor personal data: requires submission.read. For a full copy as a file use export_form_submissions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoSite slug or id to act in (multisite). Omit to use this server's default site. Call list_sites to see what exists — an empty tree or search usually means the wrong site, not missing content.
limitNoPage size, 1-200 (default 50).
formIdNoLimit to one form's submissions (its formId from list_forms). Omit for all forms.
offsetNoRows to skip, for paging (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.3
    • changedInput schema / properties / formId / description
      Previous value: -"Limit to one form's submissions (documentId of the Form)."New value: +"Limit to one form's submissions (its formId from list_forms). Omit for all forms."
    • addedInput schema / properties / limit / description
      Added value: +"Page size, 1-200 (default 50)."
    • addedInput schema / properties / offset / description
      Added value: +"Rows to skip, for paging (default 0)."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations give readOnlyHint, but the description adds genuinely new behavioral context: newest-first ordering, pagination, a permission requirement ('requires submission.read' for visitor personal data), and the important snapshot semantics where labels reflect submission time and resist later form edits.

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?

Three dense sentences, front-loaded with the core list scope, then behavior, then the alternative. Every sentence adds distinct value with no filler.

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 exists, yet the description covers what comes back (submissions with historical field-label snapshots), ordering, and paging. Combined with full schema coverage and readOnly annotations, an agent has everything needed to call it correctly.

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 description coverage is 100%, so all four parameters (site, limit, formId, offset) are already documented in the schema. The description adds nothing per-parameter, so the baseline 3 applies.

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 and resource ('List form submissions') plus scope ('in this site') and ordering ('newest first'). It also implicitly distinguishes itself from export_form_submissions and get_form_submission by describing itself as a paged list rather than a file or a single record.

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?

Explicitly routes the agent to export_form_submissions when a file copy is wanted, and states the paging model ('one page at a time'). It does not mention get_form_submission for single-record retrieval, so guidance is clear but not exhaustive.

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