Google Forms API

# Fix list: Google Forms API

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/google-forms, the October 2026 research run, assessed 8 October 2026. Grade BB, 70.8 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Google Forms API: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Payments & pricing, 35 out of 100, up to 8.1 more on the total

Why it scored 35: No x402, MPP or L402 (0). Standard use is free within published quotas, but the charge for exceeding them, planned for later in 2026, has no published price (15 of 20). No charge and no card needed to enable the API, though watches need Cloud Pub/Sub with billing enabled (20). A person creates a Cloud project and an OAuth consent screen and grants consent (0). Total 35.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 2. Security & auth, 66 out of 100, up to 6 more on the total

Why it scored 66: OAuth 2.0 with six scopes and short-lived revocable tokens (30), less 10 because the discovery document lists access_token, oauth_token and key as URL query parameters (20). forms.body.readonly and forms.responses.readonly split structure from answers and drive.file limits an app to chosen files, but nothing confirms a deleteItem and no scope is narrower than one form (17 of 20). Responses are text written by respondents, and we found no prompt-injection guidance in the Forms API docs (0 of 15). The Drive log events page records access through Workspace APIs as Item content accessed with the API method, for Workspace admins. It doesn't name the Forms API, and no per-call log for personal accounts was found (9 of 15). `security.txt` valid to 1 April 2030, Google's vulnerability reward programme, and Google's SOC 2 page lists Google Forms (20). Total 66.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 3. Agent ergonomics, 72 out of 100, up to 4.6 more on the total

Why it scored 72: Responses size with a fields mask and pageSize, and batchUpdate returns the form only when includeFormInResponse is set. forms.responses.list returns up to 5,000 responses when no pageSize is given (20 of 25). pageSize, pageToken and a timestamp filter on responses, but no other filter and no method that lists forms, which needs the Drive API (14 of 20). Standard Google error bodies with a status and a reason, as a 401 showed on 8 October, thinly documented for Forms (12 of 20). Atomic batches, a revision check through writeControl and a caller-chosen watchId, but no idempotency key on forms.create (13 of 20). Google API client libraries for Go, Java, .NET, Node.js, PHP, Python and Ruby. A new form takes two calls, three with publishing (13 of 15). Total 72.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 4. Schema & documentation, 78 out of 100, up to 3.6 more on the total

Why it scored 78: Google publishes a discovery document, not OpenAPI, which is a machine-readable contract all the same, at revision 20261004 with 10 methods and 64 schemas (25). `llms.txt` returned 404 at developers.google.com, `/workspace` and `/workspace/forms` on 8 October, but doc pages return Markdown when `.md.txt` is appended to the URL; we found no index or link that advertises it (5 of 10). Reference pages say what each method does and where it stops, such as forms.create copying only the title, but that description points to a forms.update method that doesn't exist and two guides still refer to Early Adopter Programme instructions (14 of 20). Typed parameters and unions with enums for choice type, event type, watch state and file type (14 of 15). Python, Node.js and Apps Script samples in the guides, but no error reference beyond an authentication troubleshooting page and 429 on the limits page (9 of 15). v1 in the path and release notes with a feed, though only two entries, and the change to unpublished forms after 30 June 2026 sits on a separate page (11 of 15). Total 78.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 5. Maintenance & community, 61 out of 100, up to 3.4 more on the total

Why it scored 61: The API's own release notes were last updated on 8 April 2025. The discovery document is at revision 20261004 and `@googleapis/forms` 11.0.1 was published on 24 September 2026 with the note update the API, and Google's notice set 30 June 2026 for the change to unpublished forms. We count the client release but mark down for the silent release notes, a judgement call (20 of 30). Client releases 7.0.0 on 3 August, 10.0.0, 11.0.0 and 11.0.1 in September 2026, all generated, with no dated API changelog entry in the 90 days (10 of 20). An issue tracker component, a developer forum and a Stack Overflow tag are listed; we didn't sample replies, and the release notes are stale (8 of 15). Current official client libraries, with `google-api-python-client` 2.201.0 on 30 September 2026 (15). Clients regenerate from discovery, the Node package moved to a Node 22 minimum through breaking majors in September 2026, and we didn't check the CI pass state (8 of 10). Total 61.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 6. Reliability, 91 out of 100, up to 1.8 more on the total

Why it scored 91: Graded on the REST API, the only surface. The Google Workspace Status Dashboard lists Forms, with an incidents feed that ran from 9 October 2025 to 25 September 2026 when read on 8 October (20). The feed's only Forms incident is 12 November 2025, 4 hours 45 minutes with Docs, Sheets and Slides, so the 90 days to 8 October are clean. The dashboard tracks the Forms product, not the API alone (30). 975 reads, 450 response-list reads and 375 writes a minute per project, with per-user figures (15). The limits page gives a truncated exponential backoff formula for 429, batchUpdate is atomic and writeControl.requiredRevisionId makes a form edit safe to retry, but forms.create has no idempotency key (11 of 15). The Workspace SLA names Google Forms at 99.9 per cent but measures Downtime in the user web interface and doesn't name the API (5 of 10). GA since 17 March 2022 (10). Total 91.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 7. Transparency & trust, 80 out of 100, up to 1.8 more on the total

Made of editorial 66, provenance 94.

Why it scored 80: Closed service under the Google APIs Terms of Service, last modified 9 November 2021, with Apache-2.0 client libraries (15 of 30). The Google privacy policy (effective 1 October 2026) covers end users, the Cloud Data Processing Addendum sets deletion within a maximum of 180 days for Workspace customers, and the Workspace API user data policy limits what apps may do with user data. We found no retention statement specific to Forms API data (18 of 30). A dated notice for the change to unpublished forms after 30 June 2026 and 90 days' notice promised before quota charges, but no stated deprecation period, and the API terms let Google discontinue an API at any time (13 of 20). The Workspace subprocessor list, last modified 23 July 2026, covers Forms among the Workspace services. It applies to Workspace customers, not personal accounts (20). Total 66.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Terms of service: read, states 6 of the 7 things a reader expects, and has 1 clause that costs points (7.1 of 10)
- Privacy policy: read, states 7 of the 8 things a reader expects, and has 1 clause that costs points (7.3 of 10)

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- The notice says API-created forms start unpublished after 30 June 2026, while the discovery document at revision 20261004 still says an unset unpublished parameter creates a published form. We didn't create a form to see which holds
- Google hasn't said when quota overage charges start or what they cost; the Workspace model page promises 90 days' notice
- The Workspace SLA measures Downtime in the user web interface; whether failures of the Forms API alone count isn't stated
- Whether Forms API calls appear in Drive log events isn't stated; the page names the Drive and Sheets APIs as examples
- unchecked: which Forms scopes Google classes as sensitive or restricted; the Forms docs have no scopes page
- unchecked: replies on Google's public issue tracker component 978479 for the Forms API
- unchecked: GitHub stars and the CI pass state of `google-api-nodejs-client`; the GitHub API answered 403
- unchecked: the SOC 2 reports themselves; we read only the public page that lists Google Forms
- unchecked: weekly PyPI downloads for `google-api-python-client`, which serves every Google API in any case
- The lead's description was right. No MCP server for Forms was found

## Weaknesses

- Push notifications go only to a Cloud Pub/Sub topic in the caller's project, which needs Cloud billing, and they carry no form or response data
- A watch expires after seven days unless renewed, with at most 20 watches per form and event type for each project
- No method lists forms or deletes one, the API can't create file upload questions, and it can't submit a response
- The release notes have two entries, the latest dated 8 April 2025, and no error reference page was found beyond authentication and 429
- forms.create copies only the title, so a ten-question form takes forms.create, forms.batchUpdate and, by the vendor's notice, forms.setPublishSettings

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Call forms.create with a title only, then add items with forms.batchUpdate. Any other field in the create body is disallowed
- Publish with forms.setPublishSettings before sharing. Google's notice says forms created through the API after 30 June 2026 start unpublished
- Pass pageSize on forms.responses.list. With none set a page can hold up to 5,000 responses. Use filter=timestamp > N to fetch only new ones
- After a Pub/Sub notification, call forms.responses.list yourself. The message holds only formId, watchId and eventType. Renew each watch within seven days
- Send writeControl.requiredRevisionId on forms.batchUpdate, and read the form before retrying a timed-out forms.create, which has no idempotency key

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.