grr

Overview Schema Source Related Servers Discussions Admin

script.processes.list

List Apps Script processes made by or on behalf of a user; filter by type, status, script, function, or time range and page through results.

Instructions

List information about processes made by or on behalf of a user, such as process type and current status [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: listScriptProcesses.

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 returned processes per page of results. Defaults to 50.
`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.
`userProcessFilter.types`	No
`userProcessFilter.endTime`	No	[query parameter] Optional field used to limit returned processes to those that completed on or before the given timestamp.
`userProcessFilter.scriptId`	No	[query parameter] Optional field used to limit returned processes to those originating from projects with a specific script ID.
`userProcessFilter.statuses`	No
`userProcessFilter.startTime`	No	[query parameter] Optional field used to limit returned processes to those that were started on or after the given timestamp.
`userProcessFilter.projectName`	No	[query parameter] Optional field used to limit returned processes to those originating from projects with project names containing a specific string.
`userProcessFilter.deploymentId`	No	[query parameter] Optional field used to limit returned processes to those originating from projects with a specific deployment ID.
`userProcessFilter.functionName`	No	[query parameter] Optional field used to limit returned processes to those originating from a script function with the given function name.
`userProcessFilter.userAccessLevels`	No

Output Schema

Name	Required	Description	Default
`processes`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 26, 2026

changedInput schema / properties / pageSize / description

Previous value: -"The maximum number of returned processes per page of results. Defaults to 50."New value: +"[query parameter] The maximum number of returned processes per page of results. 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 / userProcessFilter.deploymentId / description

Previous value: -"Optional field used to limit returned processes to those originating from projects with a specific deployment ID."New value: +"[query parameter] Optional field used to limit returned processes to those originating from projects with a specific deployment ID."

changedInput schema / properties / userProcessFilter.endTime / description

Previous value: -"Optional field used to limit returned processes to those that completed on or before the given timestamp."New value: +"[query parameter] Optional field used to limit returned processes to those that completed on or before the given timestamp."

addedInput schema / properties / userProcessFilter.endTime / format
```
Added value: +"google-datetime"
```

changedInput schema / properties / userProcessFilter.functionName / description

Previous value: -"Optional field used to limit returned processes to those originating from a script function with the given function name."New value: +"[query parameter] Optional field used to limit returned processes to those originating from a script function with the given function name."

changedInput schema / properties / userProcessFilter.projectName / description

Previous value: -"Optional field used to limit returned processes to those originating from projects with project names containing a specific string."New value: +"[query parameter] Optional field used to limit returned processes to those originating from projects with project names containing a specific string."

changedInput schema / properties / userProcessFilter.scriptId / description

Previous value: -"Optional field used to limit returned processes to those originating from projects with a specific script ID."New value: +"[query parameter] Optional field used to limit returned processes to those originating from projects with a specific script ID."

changedInput schema / properties / userProcessFilter.startTime / description

Previous value: -"Optional field used to limit returned processes to those that were started on or after the given timestamp."New value: +"[query parameter] Optional field used to limit returned processes to those that were started on or after the given timestamp."

addedInput schema / properties / userProcessFilter.startTime / format
```
Added value: +"google-datetime"
```

changedInput schema / properties / userProcessFilter.statuses / items / description

Previous value: -"Optional field used to limit returned processes to those having one of the specified process statuses."New value: +"[query parameter] Optional field used to limit returned processes to those having one of the specified process statuses. Values: `PROCESS_STATUS_UNSPECIFIED` = Unspecified status.; `RUNNING` = The process is currently running.; `PAUSED` = The process has paused.; `COMPLETED` = The process has completed.; `CANCELED` = The process was cancelled.; `FAILED` = The process failed.; `TIMED_OUT` = The process timed out.; `UNKNOWN` = Process status unknown.; `DELAYED` = The process is delayed, waiting for quota.; `EXECUTION_DISABLED` = AppsScript executions are disabled by Admin.."

changedInput schema / properties / userProcessFilter.types / items / description

Previous value: -"Optional field used to limit returned processes to those having one of the specified process types."New value: +"[query parameter] Optional field used to limit returned processes to those having one of the specified process types. Values: `PROCESS_TYPE_UNSPECIFIED` = Unspecified type.; `ADD_ON` = The process was started from an add-on entry point.; `EXECUTION_API` = The process was started using the Apps Script API.; `TIME_DRIVEN` = The process was started from a time-based trigger.; `TRIGGER` = The process was started from an event-based trigger.; `WEBAPP` = The process was started from a web app entry point.; `EDITOR` = The process was started using the Apps Script IDE.; `SIMPLE_TRIGGER` = The process was started from a G Suite simple trigger.; `MENU` = The process was started from a G Suite menu item.; `BATCH_TASK` = The process was started as a task in a batch job.."

changedInput schema / properties / userProcessFilter.userAccessLevels / items / description

Previous value: -"Optional field used to limit returned processes to those having one of the specified user access levels."New value: +"[query parameter] Optional field used to limit returned processes to those having one of the specified user access levels. Values: `USER_ACCESS_LEVEL_UNSPECIFIED` = User access level unspecified; `NONE` = The user has no access.; `READ` = The user has read-only access.; `WRITE` = The user has write access.; `OWNER` = The user is an owner.."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "nextPageToken": {
+      "type": "string"
+    },
+    "processes": {
+      "items": {
+        "properties": {
+          "duration": {
+            "type": "string"
+          },
+          "functionName": {
+            "type": "string"
+          },
+          "processStatus": {
+            "enum": [
+              "PROCESS_STATUS_UNSPECIFIED",
+              "RUNNING",
+              "PAUSED",
+              "COMPLETED",
+              "CANCELED",
+              "FAILED",
+              "TIMED_OUT",
+              "UNKNOWN",
+              "DELAYED",
+              "EXECUTION_DISABLED"
+            ],
+            "type": "string"
+          },
+          "processType": {
+            "enum": [
+              "PROCESS_TYPE_UNSPECIFIED",
+              "ADD_ON",
+              "EXECUTION_API",
+              "TIME_DRIVEN",
+              "TRIGGER",
+              "WEBAPP",
+              "EDITOR",
+              "SIMPLE_TRIGGER",
+              "MENU",
+              "BATCH_TASK"
+            ],
+            "type": "string"
+          },
+          "projectName": {
+            "type": "string"
+          },
+          "runtimeVersion": {
+            "enum": [
+              "RUNTIME_VERSION_UNSPECIFIED",
+              "DEPRECATED_ES5",
+              "V8"
+            ],
+            "type": "string"
+          },
+          "startTime": {
+            "type": "string"
+          },
+          "userAccessLevel": {
+            "enum": [
+              "USER_ACCESS_LEVEL_UNSPECIFIED",
+              "NONE",
+              "READ",
+              "WRITE",
+              "OWNER"
+            ],
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the burden but adds useful operation context: [HTTP GET], the precedence rule (typed flags win over `params`), and `body_file` sourcing. It omits auth requirements, rate limits, and pagination guidance, though those are partly inferable from the schema.

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?

Purpose is front-loaded, but a large share of the text is generic request-plumbing boilerplate ('request bodies are built from the typed parameters...') that repeats schema wording rather than earning space with tool-specific value.

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?

Output schema exists, so return values need not be explained, and the list purpose is clear. But for a 15-parameter nested filter tool, the description leaves the sibling distinction and filtering intent implicit.

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 80%, so the described parameters already carry full documentation. The description restates the typed-vs-`params` precedence and `body_file` behavior that the schema also documents, adding no new per-parameter 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?

States a specific verb+resource ('List information about processes made by or on behalf of a user') with concrete fields (process type, status). It names the sibling listScriptProcesses but does not explain how it differs, so differentiation is absent.

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 when-to-use or when-not-to-use guidance. The sibling is named but no condition selecting one over the other is given, leaving the agent to infer routing from the schema.

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

Deploy Server