Skip to main content
Glama

list_form_responses

List submitted responses from a Google Form with response IDs, timestamps, and answer counts. Use pagination to browse or export responses.

Instructions

List submitted responses for a Google Form with basic metadata (response IDs, timestamps, answer counts). Paginated.

Use this to discover response IDs and submission times, then call get_form_response with a specific responseId to pull the full answer payload. For the form's structure (questions, options), use get_form.

Requires OAuth scope: https://www.googleapis.com/auth/forms.responses.readonly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address. Required.
form_idYesThe form ID — the string after `/forms/d/` in the edit URL.
page_sizeNoMaximum number of responses per page. Defaults to 10. Google's hard cap is 5000; practical cap depends on response payload size. Use smaller values (10–100) for UI-facing calls and larger (500–5000) for batch export.
page_tokenNoOpaque token from a prior call's `Next page token` line. Omit to fetch the first page. Tokens are one-shot — never reuse the same token across sessions.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It correctly identifies as a read operation (OAuth read scope). Mentions pagination and basic metadata. Could be improved by noting it only returns submitted responses and any rate limits, but still good.

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?

Concise, front-loaded with main purpose, then usage flow, then auth. Every sentence adds value. No fluff.

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 4 parameters, output schema present, the description covers purpose, usage guidance, pagination, auth, and integration with siblings. No gaps.

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. Description adds value by explaining page_size caps and default, page_token one-shot nature, and required OAuth scope, going beyond schema descriptions.

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?

Clearly states it lists form responses with basic metadata (response IDs, timestamps, answer counts) and is paginated. Distinguished from sibling tools like get_form_response (full payload) and get_form (structure).

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?

Explicitly guides to use this for discovery of response IDs and timestamps, then use get_form_response for full details, and get_form for form structure. Provides clear when-to-use and when-not-to-use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HuntsDesk/ve-gws'

If you have feedback or need assistance with the MCP directory API, please join our Discord server