grr

Overview Schema Source Related Servers Discussions Admin

script.projects.deployments.get

Retrieves a specific Apps Script project deployment by script and deployment IDs, returning its details as JSON.

Instructions

Gets a deployment of an Apps Script project [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: create, delete, 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.
`deploymentId`	Yes	[URL path segment] The deployment ID.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / deploymentId / description

Previous value: -"The deployment ID."New value: +"[URL path segment] The deployment ID."

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

A3.5/5.0

Behavior3/5

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

With no annotations, the description does disclose that this is an HTTP GET and explains how requests are built (typed flags winning over the params map, body_file for whole bodies). However, it omits read-only guarantees, permission/auth requirements, and any behavioral notes about the deployment resource itself.

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 purpose is front-loaded in the first sentence. The second sentence about request construction is somewhat boilerplate for a GET call and adds length that doesn't earn much, but the whole is still compact.

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, so return-value documentation is unnecessary, and the required parameters are covered by the schema. For a simple GET of a deployment, the description is nearly complete, missing only usage context and any auth/behavior notes.

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 schema already documents scriptId, deploymentId, params, query, dry_run, and body_file. The description's note that typed flags win over the params map duplicates what the params property description already states, adding little new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource ('Gets a deployment of an Apps Script project') and flags the HTTP GET verb. It also names the sibling operations (create, delete, list, update) over the same resource, which helps distinguish it, though it stops short of explaining semantic differences.

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

Usage Guidelines3/5

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

Listing the sibling operations implies that this tool is the 'read a single deployment' option, but it never states when to use get vs list or what conditions favor it. The usage is only implied through the verb name.

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

Deploy Server