grr

Overview Schema Source Related Servers Discussions Admin

script.projects.deployments.create

Creates an Apps Script project deployment from a deployment configuration, linking a script ID, version, manifest file, and description; blocked in read-only profiles.

Instructions

Creates a deployment of an Apps Script project [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON DeploymentConfig object accepting description, manifestFileName, scriptId, versionNumber; pass it via params or whole via body_file Siblings over the same resource: delete, get, list, update.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`scriptId`	Yes	[URL path segment] The script project's Drive ID.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON DeploymentConfig object.
`request_body`	No	Request body of type DeploymentConfig: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

Name	Required	Description	Default
`updateTime`	No
`entryPoints`	No
`deploymentId`	No
`deploymentConfig`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / body_file / description

Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON DeploymentConfig object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type DeploymentConfig: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "description": {
+      "type": "string"
+    },
+    "manifestFileName": {
+      "type": "string"
+    },
+    "scriptId": {
+      "type": "string"
+    },
+    "versionNumber": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / scriptId / description

Previous value: -"The script project's Drive ID."New value: +"[URL path segment] The script project's Drive ID."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "deploymentConfig": {
+      "properties": {
+        "description": {
+          "type": "string"
+        },
+        "manifestFileName": {
+          "type": "string"
+        },
+        "scriptId": {
+          "type": "string"
+        },
+        "versionNumber": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "deploymentId": {
+      "type": "string"
+    },
+    "entryPoints": {
+      "items": {
+        "properties": {
+          "addOn": {
+            "properties": {
+              "addOnType": {
+                "enum": [
+                  "UNKNOWN_ADDON_TYPE",
+                  "GMAIL",
+                  "DATA_STUDIO"
+                ],
+                "type": "string"
+              },
+              "description": {
+                "type": "string"
+              },
+              "helpUrl": {
+                "type": "string"
+              },
+              "postInstallTipUrl": {
+                "type": "string"
+              },
+              "reportIssueUrl": {
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "entryPointType": {
+            "enum": [
+              "ENTRY_POINT_TYPE_UNSPECIFIED",
+              "WEB_APP",
+              "EXECUTION_API",
+              "ADD_ON"
+            ],
+            "type": "string"
+          },
+          "executionApi": {
+            "properties": {
+              "entryPointConfig": {
+                "properties": {
+                  "access": {
+                    "enum": [
+                      "UNKNOWN_ACCESS",
+                      "MYSELF",
+                      "DOMAIN",
+                      "ANYONE",
+                      "ANYONE_ANONYMOUS"
+                    ],
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              }
+            },
+            "type": "object"
+          },
+          "webApp": {
+            "properties": {
+              "entryPointConfig": {
+                "properties": {
+                  "access": {
+                    "enum": [
+                      "UNKNOWN_ACCESS",
+                      "MYSELF",
+                      "DOMAIN",
+                      "ANYONE",
+                      "ANYONE_ANONYMOUS"
+                    ],
+                    "type": "string"
+                  },
+                  "executeAs": {
+                    "enum": [
+                      "UNKNOWN_EXECUTE_AS",
+                      "USER_ACCESSING",
+                      "USER_DEPLOYING"
+                    ],
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "url": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "updateTime": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the load and does so well: it discloses the mutation nature, the --readonly safety refusal, and that the response is the API resource serialized as JSON. It does not mention permission/scope requirements or whether a new deployment is immediately live, which keeps it from a 5.

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?

Purpose and the HTTP verb are front-loaded, and every clause carries information. The sentence is long and compounds purpose, side effects, return type, and body routing into one block, which costs some scannability.

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?

An output schema exists, yet the description still does the important work for a no-annotation mutation tool: write semantics, safety-profile refusal, body shape, and body-delivery mechanism. Remaining gaps (permissions needed, effect of versionNumber) are modest given the rich schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds genuine routing value: it spells out the DeploymentConfig fields and explains the two mutually alternative body paths (params merge vs whole body_file). That disambiguation is not obvious from the schema alone.

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?

States a specific verb and resource ("Creates a deployment of an Apps Script project") and explicitly enumerates the sibling operations over the same resource (delete, get, list, update), so an agent can place it in the CRUD family instantly. No ambiguity about what is produced.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the sibling set over the same resource and flags that the call is refused under --readonly profiles, which is a real gating condition. It stops short of an explicit routing rule (e.g. "use update to change an existing deployment's version"), so the agent must infer when create is preferable to update.

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

Deploy Server