Sign in Book a demo
Back to Tools
Productivity & Docs OAuth
Build Your Agent View Google Forms Docs
google-forms logo

Google Forms MCP Tools for AI Agents

Let an agent create and copy forms, inspect questions and settings, collect responses, and analyze answer distributions.

Available Tools

20 tools available in this integration

GoogleForms.AggregateResponses

Return aggregate response counts and text-answer distributions for a form.

GoogleForms.CopyForm

Duplicate an existing Google Form, optionally renaming and targeting a folder.

GoogleForms.CreateForm

Create a new Google Form with a title and return its IDs and URLs.

GoogleForms.CreateWatch

Create a watch that notifies Pub/Sub when the form has new responses or schema changes.

GoogleForms.DeleteWatch

Delete a form watch, stopping Pub/Sub notifications for that subscription.

GoogleForms.GenerateGoogleFilePickerUrl

Generate a Google File Picker URL for user-driven form selection and authorization.

GoogleForms.GetForm

Fetch the normalized form structure including items, settings, and revision info.

GoogleForms.GetFormSummary

Return a concise summary of a Google Form for quick triage and discovery.

GoogleForms.GetResponse

Retrieve a single Google Form response by its response ID.

GoogleForms.ListForms

List Google Forms filtered by a discovery mode such as recent, shared, or in_folder.

GoogleForms.ListPermissions

Return normalized Drive permissions for a Google Form.

GoogleForms.ListResponses

List submitted responses for a Google Form.

GoogleForms.ListWatches

List the Pub/Sub watches currently registered on a form.

GoogleForms.RestoreForm

Restore a trashed Google Form back into the user's Drive.

GoogleForms.SetFormSettings

Update form-wide settings (quiz mode, email collection) safely.

GoogleForms.SetPublishSettings

Update a form's publish/response-accepting state.

GoogleForms.TrashForm

Move a Google Form to the Drive trash (soft delete).

GoogleForms.UpdateForm

Apply a batch of structural updates to a Google Form.

GoogleForms.UpdateWatch

Renew a form watch before it expires (watches last up to 7 days).

GoogleForms.WhoAmI

Return the authenticated Google identity (email and display name).

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find the customer feedback form, summarize its questions and response counts, and flag missing fields." Arcade picks the right Google Forms actions without making it discover form IDs first.

Up to 100x fewer tokens

Google Forms listings and summaries return concise form structure and response metadata first, while full definitions or individual responses are fetched only when needed, so the agent avoids loading every answer into context.

Complete the workflow end to end

Find the form, inspect its questions, read or aggregate responses, update settings or structure, and publish or archive it through one toolkit designed around the complete form-management task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Google Forms

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Google Forms, you can implement some of these policies:

Access when tools are listed for a user
  • Hide GoogleForms.TrashForm from agents unless the roles your IDP marks as Drive owners are active, so regular users cannot move shared forms to the trash.
  • Restrict GoogleForms.SetPublishSettings to form owners and designated survey administrators, so an agent cannot stop accepting responses or publish a form for an entire organization.
  • Show GoogleForms.UpdateForm only to agents operating under your form-editor role, so unreviewed automation cannot alter questions, answer options, or required fields.
Pre-execution before each tool call
  • Require human approval before GoogleForms.TrashForm runs, so an agent cannot remove a form that still collects business records.
  • Block GoogleForms.SetFormSettings when it enables quiz mode or email collection without an approved form change, so an agent cannot change how respondents are evaluated or identified.
  • Require human approval before GoogleForms.CreateWatch runs on a form containing employee, customer, or student responses, so new submissions are not forwarded to an unapproved Pub/Sub subscription.
Post-execution after the tool returns
  • Redact respondent names, email addresses, free-text answers, and uploaded-file references from GoogleForms.ListResponses results before they reach the model.
  • Strip email addresses, phone numbers, postal addresses, and free-text answers from GoogleForms.GetResponse results unless the agent is handling an approved case.
  • Redact personal email addresses and permission-change details from GoogleForms.ListPermissions results, so the model sees access roles without exposing individual collaborators' contact information.

How to use Google Forms with your agent

Pick an MCP client below and follow the walkthrough to connect Google Forms to your agent. Each end user authorizes their own Google account.

Your questions, answered

A Google Forms MCP server exposes form operations as structured tools that an AI agent can call through the Model Context Protocol. After a user authorizes their Google account, the agent can create, inspect, update, publish, and analyze forms within the permissions that user approved.

Google Forms provides APIs for working with forms, but Arcade turns those capabilities into an MCP-accessible actions runtime. Arcade adds per-user OAuth, agent-optimized actions, approval workflows, redaction, and scope controls for teams using different agents and clients.

Agents can find forms by recency, sharing, or folder; inspect form structure and permissions; create or copy forms; read individual or aggregate responses; update questions and settings; control whether a form accepts responses; create and renew response watches; and trash or restore forms.

Each user grants the Google OAuth permissions required by the actions they use. Reading forms and responses needs read access, while creating, copying, updating, publishing, moving, or restoring forms needs the corresponding write access to Forms and, where applicable, Drive; grant the narrowest scopes that support the workflow.

Yes. Each user authorizes their own Google account through OAuth, and Google Forms actions run under that user's authorization grant. An agent can access only the forms and permissions that user has approved.

Yes. Contextual Access policies can require human approval before consequential Google Forms actions such as changing form structure or settings, publishing or closing responses, or moving a form to the trash. The call proceeds only after the policy's conditions have been satisfied.

Arcade proxies Google Forms API calls and does not persist your form content or responses as part of normal tool execution. OAuth credentials are brokered and stored encrypted at rest, and the model never receives raw credentials.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the user's Google authorization remains valid. If access is revoked, rotated, or can no longer be refreshed, Google Forms actions stop until the user reconnects their account.

Calls remain subject to Google's Google Forms and Drive API quotas and any limits on response watches or request volume. Arcade does not remove those Google limits, so high-volume workflows should handle throttling and retries.

Ready to actually ship your agent?

Connect your agent to Google Forms with managed OAuth, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Google Forms Quickstart