Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Create Form

create_form

Create a Google Form by providing a title and optional description. Define the form's purpose and structure directly from your request.

Instructions

Create a new form using the title given in the provided form message in the request.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	The title of the form.
`description`	No	The description of the form.
`document_title`	No	The document title (shown in browser tab).
`user_google_email`	Yes	The user's Google email address. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.28.0Sep 24, 2026
- removedInput schema / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / description / type
```
Added value: +"string"
```
- removedInput schema / properties / document_title / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / document_title / type
```
Added value: +"string"
```

Changed13 schema fields changedv1.0.1Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / description / description
```
Added value: +"The description of the form."
```
removedInput schema / properties / description / title
```
Removed value: -"Description"
```

addedInput schema / properties / document_title / description

Added value: +"The document title (shown in browser tab)."

removedInput schema / properties / document_title / title
```
Removed value: -"Document Title"
```

removedInput schema / properties / service

Removed value: -{
-  "title": "service",
-  "type": "string"
-}

addedInput schema / properties / title / description
```
Added value: +"The title of the form."
```
removedInput schema / properties / title / title
```
Removed value: -"Title"
```
addedInput schema / properties / user_google_email / description
```
Added value: +"The user's Google email address. Required."
```
removedInput schema / properties / user_google_email / title
```
Removed value: -"User Google Email"
```

changedInput schema / required

Previous value: -[
-  "service",
-  "user_google_email",
-  "title"
-]New value: +[
+  "user_google_email",
+  "title"
+]

removedInput schema / title
```
Removed value: -"create_formArguments"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv1.0.0Jun 10, 2025

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already indicate this is a non-read-only, non-idempotent operation, and the description reinforces that by saying it creates a new form. That adds a small amount of context beyond the annotations, but the description does not disclose side effects, authorization requirements, or response behavior. There is no contradiction with annotations.

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 description is a single concise sentence with no filler. It is slightly awkward due to the 'provided form message in the request' phrasing, but it remains short and front-loads the primary action.

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

Completeness3/5

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

The tool has an output schemaahan, full schema coverage, and annotations, so the description does not need to document return values or safety. However, the vague reference to 'form message' and the lack of usage guidance leave some ambiguity about how the request supplies the title and when this tool is appropriate.

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 is 100%, so the parameters are already fully documented in the schema. The description mentions the title but adds no meaning beyond the schema descriptions. It does not clarify how 'description' or 'document_title' are used or how user_google_email affects execution.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: 'Create a new form'. It is semantically distinct from sibling tools like get_form, batch_update_form, and set_publish_settings. However, the phrase 'using the title given in the provided form message in the request' is somewhat vague and could be interpreted ambiguously.

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 explicit guidance is given about when to use this tool versus alternatives, nor any conditions or exclusions. The only hint is the verb 'Create', which implies it is for creating a new form rather than retrieving or updating one, but this is left entirely to inference.

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

Deploy Server