grr

Overview Schema Source Related Servers Discussions Admin

script.projects.deployments.list

Lists deployments for an Apps Script project, with pagination via pageSize and pageToken, and returns the results as JSON for inspection or management.

Instructions

Lists the deployments 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, get, 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.
`pageSize`	No	[query parameter] The maximum number of deployments on each returned page. Defaults to 50.
`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.
`pageToken`	No	[query parameter] The token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from a previous response.

Output Schema

Name	Required	Description	Default
`deployments`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 26, 2026

changedInput schema / properties / pageSize / description

Previous value: -"The maximum number of deployments on each returned page. Defaults to 50."New value: +"[query parameter] The maximum number of deployments on each returned page. Defaults to 50."

addedInput schema / properties / pageSize / format
```
Added value: +"int32"
```

changedInput schema / properties / pageToken / description

Previous value: -"The token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from a previous response."New value: +"[query parameter] The token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from a previous response."

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": {
+    "deployments": {
+      "items": {
+        "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": {
+                      "type": "object"
+                    }
+                  },
+                  "type": "object"
+                },
+                "webApp": {
+                  "properties": {
+                    "entryPointConfig": {
+                      "type": "object"
+                    },
+                    "url": {
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "updateTime": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextPageToken": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that this is an HTTP GET returning JSON, which establishes a read-only profile. However, pagination behavior (pageSize/pageToken round-tripping), required auth scopes, and result ordering are not described, and the boilerplate about building request bodies is irrelevant for a GET.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well front-loaded, but the remainder is generic boilerplate about typed parameters and `body_file` that has little bearing on a read-only list endpoint, diluting the signal. It is not bloated, but a meaningful share of the text does not earn its place for this specific tool.

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 and the input schema fully documents all seven parameters, so the definition needn't explain return values or parameter formats. The remaining gap — pagination loop guidance and auth requirements — is modest for a tool of this complexity.

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 pageSize, pageToken, scriptId, and body_file are already fully documented; baseline is 3. The description does add one semantic note — typed flags win over the `params` map — which slightly clarifies the merge precedence, but nothing about pagination semantics is added.

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?

Opens with a specific verb+resource+scope: 'Lists the deployments of an Apps Script project [HTTP GET]'. It also names the sibling operations on the same resource (create, delete, get, update), though it doesn't say what distinguishes list from them beyond the verb. The core purpose is unambiguous.

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?

Naming the siblings implies this is the enumeration variant versus the CRUD variants, which is helpful implied guidance. But there is no explicit statement of when to use list versus get, no prerequisites, and no mention of pagination-driven repeated calls — usage must be inferred.

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

Deploy Server