google-appscript-mcp-server

list_script_processes

List executed processes for a Google Apps Script project, filtered by time, status, function, or deployment.

Instructions

List information about a script's executed processes.

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": {
      "scriptId": "<scriptId>"
    },
    "name": "list_script_processes"
  }
}

Input Schema

Name	Required	Description
`types`	No	Filter by process types.
`endTime`	No	Filter by end time.
`pageSize`	No	The number of processes to return per page.
`scriptId`	Yes	The ID of the script to list processes for.
`statuses`	No	Filter by process statuses.
`pageToken`	No	Token for pagination.
`startTime`	No	Filter by start time.
`deploymentId`	No	Filter by deployment ID.
`functionName`	No	Filter by function name.
`userAccessLevels`	No	Filter by user access levels.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 2, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description must disclose behavior itself, but it only states the action. It does not mention pagination, filtering behavior, authentication needs, or what happens with invalid inputs. This is a read operation but that is not explicitly stated.

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 description is a single sentence and front-loaded, which is concise. However, given the tool has 10 parameters and no output schema, the brevity borders on under-specification rather than effective conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is moderately complex with 10 parameters, no output schema, and no annotations. The description provides only the basic action, omitting return value structure, pagination defaults, and relationships with sibling tools, making it incomplete for an agent to invoke correctly.

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 fully documents all 10 parameters. The description adds no additional meaning beyond the generic action, which is the baseline expected when schema covers everything.

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 uses a specific verb ('List') and resource ('script's executed processes'), making the core action clear. However, it does not differentiate this tool from the similarly named sibling 'script_processes_list', so it loses a point for missing sibling distinction.

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?

There is no guidance on when to use this tool versus alternatives like 'script_processes_list' or 'recent_executions'. It does not state any prerequisites or intended scenarios, leaving the agent without decision support.

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