Connect the Google Apps Script MCP server to your AI agent Open source, MIT, on npm. Setup instructions for Claude, Cursor and Codex are in the repository; adoption questions — Telegram. GitHub repository Telegram

Google Apps Script: List execution processes — MCP tool

Google Apps Script MCP tool: Reads the execution history — which functions ran, when, and which failed.

Technical name: list_processes

What task it solves

I want to see which script executions ran and which failed.

Lists execution processes: function name, launch type (web app, API call, time trigger, ...), status (COMPLETED, FAILED, TIMED_OUT, ...), start time and duration.

When to use it

Use it to audit a script's activity or hunt failures: filter statuses=["FAILED","TIMED_OUT"] and a time window. With script_id only that script's executions are listed; without it, all executions started by the authorizing user.

What to provide

  • script_idoptional. Limit to one script.
  • function_name, deployment_idoptional filters.
  • statuses, typesoptional. Process states / launch types to keep.
  • start_time, end_timeoptional. RFC3339 UTC bounds on the process start.
  • page_size (1..50), page_tokenoptional pagination.

What it returns

processes[] with projectName, functionName, processType, processStatus, userAccessLevel, startTime, duration, plus nextPageToken.

What changes in Google Apps Script

Nothing — this is a pure read.

Example request

Show me the failed executions of script 1AbC... in the last 24 hours — which function keeps failing?

Errors and limitations

Requires the script.processes scope. The API reports the fact and timing of a failure, never the error message or logs — get the message by re-running via run_function, or from the Apps Script dashboard / Cloud Logging. History is the user's own executions.

Access also depends on token permissions, quotas, and upstream API limits.

Related MCP tools

Technical details