Skip to main content
Glama

Pagetool

List form entries for a site

list_form_submissions
Read-onlyIdempotent

Lists the entries visitors sent through a site's built-in forms, newest first: the submitted fields, whether the notification email was sent, and when. Optional form_key narrows it to one form. limit defaults to 50 (max 200). No visitor IP data is returned. Test entries sent from a staged preview are left out unless include_preview is true. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many entries, newest first. Default 50, max 200.
form_keyNoOptional: only entries from this form.
site_keyYesThe site whose form entries to list. Must be yours.
include_previewNoAlso list test entries sent from a staged preview (they are marked as preview entries). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new traits: newest-first ordering, confirmation that no visitor IP data is returned, exclusion of staged-preview test entries unless opted in, and that the call is free - all relevant to an agent deciding whether and how to call it.

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?

Four compact sentences with the core behavior and ordering front-loaded, followed by parameter behavior, then privacy and cost caveats. Every clause carries information; nothing is redundant 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?

With no output schema, the description compensates by naming what each entry contains (submitted fields, notification-email status, timestamp) and what is deliberately absent (visitor IPs, preview entries by default). For a four-parameter read-only list tool, 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% and the description largely restates the same facts (limit default 50/max 200, form_key narrowing, include_preview behavior). It reinforces the semantics but adds no syntax, format, or edge-case detail beyond what the schema already documents, so the baseline of 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 - listing entries visitors submitted through a site's built-in forms - plus the sort order (newest first). The resource is clearly distinct from sibling list tools such as list_pages, list_reviews, and list_sections, so an agent can select it without opening the schema.

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?

Gives clear conditional usage: form_key narrows results to a single form, include_preview is required to surface staged-preview test entries, and limit defaults to 50 with a max of 200. It stops short of naming an explicit alternative tool or stating when-not-to-use, but the filtering conditions cover the practical decision points.

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