google-workspace-mcp-advanced

list_script_processes

List Apps Script processes for a specified user, with optional filtering by script ID and pagination.

Instructions

List Apps Script processes.

If script_id is provided, uses script-specific process listing. Otherwise, uses user-wide process listing.

Args: user_google_email: The user's Google email address. Required. script_id: Optional script ID for script-specific listing. script_process_filter_json: Optional JSON object for script process filter. user_process_filter_json: Optional JSON object for user process filter. page_size: Number of results to return. Defaults to 50. page_token: Optional pagination token.

Returns: str: Process list summary.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_google_email": "<user_google_email>"
    },
    "name": "list_script_processes"
  }
}

Input Schema

Name	Required	Description	Default
`user_google_email`	Yes
`script_id`	No
`script_process_filter_json`	No
`user_process_filter_json`	No
`page_size`	No
`page_token`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.10Jun 2, 2026

TDQS

A3.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It describes the listing behavior but does not disclose whether the operation is read-only, idempotent, or has side effects. It also omits authentication requirements or rate limits, leaving gaps in behavioral transparency.

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 concise: a brief header followed by a compact list of arguments. Every sentence is necessary, and it is front-loaded with the main purpose. No fluff or redundancy.

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?

The description covers the core functionality and parameters adequately, including pagination. However, it lacks details on the output format (beyond 'summary'), error handling, and the expected format of filter JSONs. Since an output schema exists, return value detail is not required, but completeness is still moderate.

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?

With 0% schema description coverage, the description adds significant value by listing and explaining each parameter, including required/optional status, default values, and purpose of filter JSONs. It compensates well for the lack of schema descriptions.

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 lists Apps Script processes and distinguishes between script-specific and user-wide listing based on the script_id parameter. It is specific and differentiated from sibling tools, none of which list script processes.

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?

The description explains when to use script-specific vs user-wide listing by indicating the role of script_id. It provides clear context for usage, though it does not explicitly compare to alternatives since no direct alternatives exist among siblings.

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

Deploy Server