Skip to main content
Glama
taylorwilsdon

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

by taylorwilsdon
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Get Form Response

get_form_response
Read-onlyIdempotent

Retrieve a single Google Form response by supplying the form ID and response ID. Access specific submissions to review or process individual answers.

Instructions

Get one response from the form.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
form_idYesThe ID of the form.
response_idYesThe ID of the response to retrieve.
user_google_emailYesThe user's Google email address. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changedv1.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / form_id / description
      Added value: +"The ID of the form."
    • removedInput schema / properties / form_id / title
      Removed value: -"Form Id"
    • addedInput schema / properties / response_id / description
      Added value: +"The ID of the response to retrieve."
    • removedInput schema / properties / response_id / title
      Removed value: -"Response Id"
    • removedInput schema / properties / service
      Removed value: -{
-  "title": "service",
-  "type": "string"
-}
    • 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",
-  "form_id",
-  "response_id"
-]New value: +[
+  "user_google_email",
+  "form_id",
+  "response_id"
+]
    • removedInput schema / title
      Removed value: -"get_form_responseArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, idempotentHint, and openWorldHint, so the safety profile is clear. The description adds no extra behavioral context, such as error behavior or return format, but it also does not contradict the annotations.

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?

The description is a single, concise sentence: 'Get one response from the form.' It is front-loaded, immediately conveys the purpose, and contains no filler or redundant information.

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?

For a simple read-only getter with a full output schema and rich annotations, the description is adequate but not fully complete. It does not mention the necessity of a response_id (though the schema covers it) or provide any context about what a response contains, but given the tool's simplicity, the missing details are minor.

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 description coverage is 100%, so the parameters are well-documented in the schema. The description does not add any additional parameter-level information, so it meets the baseline but does not exceed it.

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 'Get one response from the form' clearly identifies the action (get) and resource (form response), with the scope 'one' distinguishing it from listing all responses (e.g., list_form_responses). It is specific and unambiguous.

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 is provided on when to use this tool versus alternatives. It does not mention that it requires a response_id or that list_form_responses should be used for multiple responses. The usage context is left entirely to inference from the schema.

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/taylorwilsdon/google_workspace_mcp'

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