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

Manage Deployment

manage_deployment

Destructive

Create, update, or delete Apps Script deployments by script ID, version, and deployment ID to manage release versions.

Instructions

Create, update, or delete Apps Script deployments.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	Action to perform - "create", "update", or "delete"
`script_id`	Yes	The script project ID
`description`	No	Deployment description (required for create; optional for update when version_number is supplied)
`deployment_id`	No	The deployment ID (required for update and delete)
`version_number`	No	Version number to point the deployment at (for update only). Required to roll a deployment forward to a newly created script version.
`user_google_email`	Yes	User's email address
`version_description`	No	Optional version description (for create only)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.28.0Sep 24, 2026
- removedInput schema / properties / deployment_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / deployment_id / type
```
Added value: +"string"
```
- removedInput schema / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / description / type
```
Added value: +"string"
```
- removedInput schema / properties / version_description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / version_description / type
```
Added value: +"string"
```
- removedInput schema / properties / version_number / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / version_number / type
```
Added value: +"integer"
```
Addedv1.0.1Jul 31, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds no behavioral traits beyond what's in the schema: 'create, update, delete' simply mirrors the action parameter values. It fails to mention irreversibility of deletes, permission requirements, or dependency on existing deployments/versions.

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, front-loaded sentence with zero filler. It efficiently communicates the core purpose without unnecessary details, making it easy for an agent to quickly grasp the tool's function.

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

Completeness2/5

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

For a tool with 7 parameters, 3 required, and a destructive operation, the description is too sparse. It omits the deployment lifecycle context (e.g., creating a deployment typically requires a version, updating requires an existing deployment_id) and provides no guidance on how the parameters interact. The output schema covers return values, but the operational context is largely missing.

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%, and the parameter descriptions are detailed (e.g., deployment_id required for update/delete, description required for create). The tool description adds no additional parameter semantics, so the baseline of 3 applies.

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 clearly states the tool's actions (create, update, delete) on a specific resource (Apps Script deployments). It distinguishes itself from siblings like list_script_deployments (read-only) and manage_script_version (version management) by directly naming the deployment resource and mutation verbs.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention list_script_deployments for viewing deployments or manage_script_version for handling versions, leaving the agent to infer usage from the sibling names alone. There is no explicit when-to-use or when-not-to-use context.

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

Deploy Server