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

Set Publish Settings

set_publish_settings

Update a Google Form's publish settings to control visibility and response collection. Set whether the form is published and accepting responses.

Instructions

Updates the publish settings of a form.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
form_idYesThe ID of the form to update publish settings for.
is_publishedNoWhether the form is published and visible to responders. Defaults to True.
user_google_emailYesThe user's Google email address. Required.
is_accepting_responsesNoWhether the form accepts responses. Only takes effect when the form is published. Defaults to True.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

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

  1. Changed13 schema fields changedv1.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / form_id / description
      Added value: +"The ID of the form to update publish settings for."
    • removedInput schema / properties / form_id / title
      Removed value: -"Form Id"
    • addedInput schema / properties / is_accepting_responses
      Added value: +{
+  "default": true,
+  "description": "Whether the form accepts responses. Only takes effect when the form is published. Defaults to True.",
+  "type": "boolean"
+}
    • addedInput schema / properties / is_published
      Added value: +{
+  "default": true,
+  "description": "Whether the form is published and visible to responders. Defaults to True.",
+  "type": "boolean"
+}
    • removedInput schema / properties / publish_as_template
      Removed value: -{
-  "default": false,
-  "title": "Publish As Template",
-  "type": "boolean"
-}
    • removedInput schema / properties / require_authentication
      Removed value: -{
-  "default": false,
-  "title": "Require Authentication",
-  "type": "boolean"
-}
    • 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"
-]New value: +[
+  "user_google_email",
+  "form_id"
+]
    • removedInput schema / title
      Removed value: -"set_publish_settingsArguments"
    • 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

B3.2/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, but the description adds no extra behavioral context, such as side effects on existing responses, required permissions, or whether changes are reversible. It does not contradict annotations, but fails to enrich them.

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, front-loaded sentence with no fluff. However, it is arguably too terse for a tool with four parameters and no guidance, though conciseness itself is well-executed.

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 presence of an output schema and complete parameter descriptions lowers the burden on the description. Still, the description does not explain when to use this tool instead of batch_update_form, nor the implications of altering publish settings. It is minimally sufficient for a simple tool but leaves gaps.

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 baseline is 3. The description provides no additional parameter meaning; the schema's own field descriptions fully document form_id, is_published, user_google_email, and is_accepting_responses.

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 uses a specific verb 'Updates' and a specific resource 'publish settings' targeting 'a form'. This clearly distinguishes it from broader tools like batch_update_form, making its purpose 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 such as batch_update_form or get_form. There are no exclusions or context cues to help an agent choose correctly.

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