Skip to main content
Glama

Get Form Submissions

get_form_submissions
Read-only

Use this when the user asks who filled out their contact form, or wants to see/export leads from their live site. Returns submissions from any built with KleapForm on the app, newest first. Empty list is normal for a brand new site with no visitors yet. Requires the forms:read scope (submissions contain visitor PII) — sessions connected BEFORE this tool shipped don't have it: on INSUFFICIENT_SCOPE the connection has NOT expired: it was authorized before this tool existed and needs one re-authorization to add the scope. Say that, never that it expired.

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": {
      "app_id": "<app_id>",
      "context": "<context>"
    },
    "name": "get_form_submissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (default 20, max 100)
sinceNoOnly return submissions at/after this ISO 8601 date, e.g. '2026-06-01T00:00:00Z'
app_idYesThe app id to fetch submissions for
contextYesWhy this call, in one short sentence. Used to improve the connector; never include credentials or personal data.

Output Schema

NameRequiredDescriptionDefault
countNo
app_idNo
submissionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/destructive annotations, it discloses ordering ('newest first'), a semantically valid empty result, the required forms:read scope, the reason for that scope (visitor PII), and how to interpret the INSUFFICIENT_SCOPE failure. That last point is especially valuable because it prevents an agent from misreporting a scope error as an expired connection.

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 guidance is front-loaded: intent trigger first, then return behavior, then scope/error handling. Every sentence carries information, though the scope-error sentence is long and packs several clauses that could be split for faster scanning.

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?

For a simple filtered read tool with an output schema already defining return shape, the description covers everything an agent needs: when to call it, ordering, empty-result meaning, auth scope, and error interpretation. Nothing material is missing.

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%, with limit, since, app_id and context all documented in the schema itself, so the baseline is 3. The description adds only the implicit 'newest first' ordering and does not elaborate on how limit or since interact with that ordering, so it does not exceed the schema.

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 names a specific verb and resource ('Returns submissions from any <form> built with KleapForm') and frames the user intent that triggers it (who filled out the contact form, export leads). It is clearly distinguishable from analytics or raw database tools in the sibling list because it is scoped to KleapForm-built forms on the live site.

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?

It gives a clear when-to-use trigger sentence plus edge-case guidance ('Empty list is normal for a brand new site with no visitors yet') and precise recovery instructions for INSUFFICIENT_SCOPE. What it lacks is any when-not or explicit pointer to an alternative sibling, so it stops short of a full routing rule.

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.