Skip to main content
Glama
dipseth

google-workspace-unlimited

Create Google Form

create_form

Create a new Google Form with a title and optional description. Returns the form ID, edit URL, and response URL.

Instructions

Create a new Google Form with customizable title, description, and document title. Returns form ID and URLs for editing and responses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesForm title displayed at the top
descriptionNoOptional description explaining the form's purpose
document_titleNoTitle shown in browser tab (defaults to main title)
user_google_emailNoThe user's Google email address for Forms access. If None, uses the current authenticated user from FastMCP context (auto-injected by middleware).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
titleYes
formIdYes
editUrlYes
messageYes
successYes
userEmailNo
responseUrlYes
Behavior3/5

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

Annotations already indicate write operation (readOnlyHint=false) and non-destructive. Description adds return info (form ID, URLs) but no additional behavioral details beyond what annotations provide.

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?

Single sentence, front-loaded, no unnecessary words. Efficiently captures purpose and key outputs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists (return values documented), description is sufficient. Could mention that created form starts empty, but sibling tool for questions compensates.

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 coverage 100% means parameters are fully documented. Description mentions title, description, document title but adds no extra semantic meaning beyond schema definitions.

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?

Description clearly states verb 'Create', resource 'new Google Form', and mentions customizable attributes and return values. Differentiates from siblings like add_questions_to_form.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives. Does not mention that it only creates the shell, and questions must be added separately.

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/dipseth/google_workspace_fastmcp2'

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