Skip to main content
Glama

get_form

Fetch a Google Form's metadata and full item list, including questions, sections, and grids, for use before editing with batch_update_form.

Instructions

Fetch a Google Form's metadata and full item list (questions, sections, grids, media items) by its form ID.

Use this before editing a form with batch_update_form — the returned item indices and itemId/questionId values are the handles you pass into update/delete requests. For response data (submitted answers), use list_form_responses or get_form_response instead.

Requires OAuth scope: https://www.googleapis.com/auth/forms.body or forms.body.readonly (read-only).

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 (NOT the full URL). Example: `1FAIpQLSe...`. Both user-owned and shared forms work if the user has at least read access.

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 the description carries full burden. It explains that the returned item indices and IDs are handles for updates, and that it requires read-only OAuth scope. It implies a read-only operation, and does not mention any destructive side effects.

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 concise paragraphs, each with a distinct purpose: stating functionality, usage guidance with sibling differentiation, and authorization requirement. No redundant or filler sentences.

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 read-only fetch tool with an existing output schema, the description fully explains purpose, usage context, and prerequisites. It also distinguishes from sibling tools for response data, making it self-contained.

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?

Input schema covers 100% of parameters with descriptions. The description adds helpful real-world context (e.g., form_id is the string after /forms/d/ in the URL, supports both user-owned and shared forms), supplementing 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 clearly states the verb 'fetch', the resource 'Google Form', and the scope 'metadata and full item list'. It distinguishes from sibling tools (list_form_responses, get_form_response) by specifying that this tool is for form structure, not response data.

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 advises using this tool before batch_update_form and distinguishes from response data tools. Mentions required OAuth scope, but does not explicitly state 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