Skip to main content
Glama
mohalmah

Google Apps Script MCP Server

by mohalmah

script_projects_versions_list

Retrieve and manage version history for Google Apps Script projects to track changes and restore previous states.

Instructions

List the versions of a Google Apps Script project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scriptIdYesThe ID of the script project.
pageSizeNoThe number of versions to return per page.
pageTokenNoThe token for the next page of results.
fieldsNoSelector specifying which fields to include in a partial response.
altNoData format for response.
keyNoAPI key for the request.
access_tokenNoOAuth access token.
oauth_tokenNoOAuth 2.0 token for the current user.
prettyPrintNoReturns response with indentations and line breaks.

Implementation Reference

  • The main handler function that executes the tool logic: authenticates via OAuth, constructs the API URL for listing script versions, makes the GET request, handles responses and errors with logging.
    const executeFunction = async ({ scriptId, pageSize = 100, pageToken, fields, key, access_token, oauth_token, prettyPrint = true }) => {
      const baseUrl = 'https://script.googleapis.com';
      const startTime = Date.now();
      
      try {
        logger.info('SCRIPT_VERSIONS_LIST', 'Starting script versions list request', { scriptId, pageSize, pageToken });
        
        // Get OAuth access token
        const token = await getOAuthAccessToken();
        
        // Construct the URL with query parameters
        const url = new URL(`${baseUrl}/v1/projects/${scriptId}/versions`);
        url.searchParams.append('pageSize', pageSize.toString());
        if (pageToken) url.searchParams.append('pageToken', pageToken);
        if (fields) url.searchParams.append('fields', fields);
        url.searchParams.append('alt', 'json');
        if (key) url.searchParams.append('key', key);
        if (prettyPrint) url.searchParams.append('prettyPrint', prettyPrint.toString());
    
        logger.debug('SCRIPT_VERSIONS_LIST', 'Constructed API URL', {
          url: url.toString(),
          pathSegments: url.pathname.split('/'),
          queryParams: Object.fromEntries(url.searchParams)
        });
    
        // Set up headers for the request
        const headers = {
          'Accept': 'application/json',
          'Authorization': `Bearer ${token}`
        };
    
        logger.logAPICall('GET', url.toString(), headers);
    
        // Perform the fetch request
        const fetchStartTime = Date.now();
        const response = await fetch(url.toString(), {
          method: 'GET',
          headers
        });
        
        const fetchDuration = Date.now() - fetchStartTime;
        const responseSize = response.headers.get('content-length') || 'unknown';
        
        logger.logAPIResponse('GET', url.toString(), response.status, fetchDuration, responseSize);
    
        // Check if the response was successful
        if (!response.ok) {
          const errorText = await response.text();
          let errorData;
          
          try {
            errorData = JSON.parse(errorText);
          } catch (parseError) {
            errorData = { message: errorText };
          }
    
          const detailedError = {
            status: response.status,
            statusText: response.statusText,
            url: url.toString(),
            errorResponse: errorData,
            duration: Date.now() - startTime,
            scriptId,
            timestamp: new Date().toISOString()
          };
    
          logger.error('SCRIPT_VERSIONS_LIST', 'API request failed', detailedError);
          
          console.error('❌ API Error Details:', JSON.stringify(detailedError, null, 2));
          
          throw new Error(`API Error (${response.status}): ${errorData.error?.message || errorData.message || 'Unknown error'}`);
        }
    
        // Parse and return the response data
        const data = await response.json();
        
        logger.info('SCRIPT_VERSIONS_LIST', 'Successfully retrieved script versions', {
          scriptId,
          versionsCount: data.versions?.length || 0,
          duration: Date.now() - startTime
        });
        
        console.log('✅ Successfully retrieved script versions');
        return data;
      } catch (error) {
        const errorDetails = {
          message: error.message,
          stack: error.stack,
          scriptId,
          duration: Date.now() - startTime,
          timestamp: new Date().toISOString(),
          errorType: error.name || 'Unknown'
        };
    
        logger.error('SCRIPT_VERSIONS_LIST', 'Error listing script versions', errorDetails);
        
        console.error('❌ Error listing script versions:', errorDetails);
        
        // Return detailed error information for debugging
        return { 
          error: true,
          message: error.message,
          details: errorDetails,
          rawError: {
            name: error.name,
            stack: error.stack
          }
        };
      }
    };
  • The tool definition including the schema for input parameters (scriptId required, optional pagination and formatting params) and tool metadata.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'script_projects_versions_list',
          description: 'List the versions of a Google Apps Script project.',
          parameters: {
            type: 'object',
            properties: {
              scriptId: {
                type: 'string',
                description: 'The ID of the script project.'
              },
              pageSize: {
                type: 'integer',
                description: 'The number of versions to return per page.'
              },
              pageToken: {
                type: 'string',
                description: 'The token for the next page of results.'
              },
              fields: {
                type: 'string',
                description: 'Selector specifying which fields to include in a partial response.'
              },
              alt: {
                type: 'string',
                enum: ['json'],
                description: 'Data format for response.'
              },
              key: {
                type: 'string',
                description: 'API key for the request.'
              },
              access_token: {
                type: 'string',
                description: 'OAuth access token.'
              },
              oauth_token: {
                type: 'string',
                description: 'OAuth 2.0 token for the current user.'
              },
              prettyPrint: {
                type: 'boolean',
                description: 'Returns response with indentations and line breaks.'
              }
            },
            required: ['scriptId']
          }
        }
      }
    };
  • tools/paths.js:1-18 (registration)
    The toolPaths array includes the path to this tool's file, allowing dynamic discovery and registration in lib/tools.js.
    export const toolPaths = [
      'google-app-script-api/apps-script-api/script-projects-deployments-delete.js',
      'google-app-script-api/apps-script-api/script-projects-create.js',
      'google-app-script-api/apps-script-api/script-projects-versions-create.js',
      'google-app-script-api/apps-script-api/script-projects-deployments-create.js',
      'google-app-script-api/apps-script-api/script-projects-deployments-update.js',
      'google-app-script-api/apps-script-api/script-projects-deployments-list.js',
      'google-app-script-api/apps-script-api/script-projects-update-content.js',
      'google-app-script-api/apps-script-api/script-projects-deployments-get.js',
      'google-app-script-api/apps-script-api/script-scripts-run.js',
      'google-app-script-api/apps-script-api/script-projects-get.js',
      'google-app-script-api/apps-script-api/script-processes-list-script-processes.js',
      'google-app-script-api/apps-script-api/script-projects-get-metrics.js',
      'google-app-script-api/apps-script-api/script-projects-get-content.js',
      'google-app-script-api/apps-script-api/script-projects-versions-list.js',
      'google-app-script-api/apps-script-api/script-projects-versions-get.js',
      'google-app-script-api/apps-script-api/script-processes-list.js'
    ];
  • lib/tools.js:8-64 (registration)
    Dynamic tool discovery function that imports apiTool from each path in toolPaths, wraps the handler with logging, and prepares tools for MCP registration.
    export async function discoverTools() {
      logger.info('DISCOVERY', `Starting tool discovery for ${toolPaths.length} tool paths`);
      
      const toolPromises = toolPaths.map(async (file) => {
        try {
          logger.debug('DISCOVERY', `Loading tool from: ${file}`);
          const module = await import(`../tools/${file}`);
          
          if (!module.apiTool) {
            logger.warn('DISCOVERY', `Tool file missing apiTool export: ${file}`);
            return null;
          }
    
          const toolName = module.apiTool.definition?.function?.name;
          if (!toolName) {
            logger.warn('DISCOVERY', `Tool missing function name: ${file}`);
            return null;
          }
    
          // Wrap the original function with logging
          const originalFunction = module.apiTool.function;
          const wrappedFunction = withLogging(toolName, originalFunction);
    
          logger.debug('DISCOVERY', `Successfully loaded tool: ${toolName}`, {
            file,
            toolName,
            description: module.apiTool.definition?.function?.description
          });
    
          return {
            ...module.apiTool,
            function: wrappedFunction,
            path: file,
          };
        } catch (error) {
          logger.error('DISCOVERY', `Failed to load tool: ${file}`, {
            file,
            error: {
              message: error.message,
              stack: error.stack
            }
          });
          return null;
        }
      });
      
      const tools = (await Promise.all(toolPromises)).filter(Boolean);
      
      logger.info('DISCOVERY', `Tool discovery completed`, {
        totalPaths: toolPaths.length,
        successfullyLoaded: tools.length,
        failed: toolPaths.length - tools.length,
        toolNames: tools.map(t => t.definition?.function?.name).filter(Boolean)
      });
      
      return tools;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'List' implies a read-only operation, the description doesn't specify whether this requires authentication, has rate limits, returns paginated results (though schema hints at pagination via pageSize/pageToken), or what the output format looks like. For a tool with 9 parameters and no annotations, this leaves significant behavioral gaps.

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 a single, clear sentence that states the core purpose without unnecessary words. It's front-loaded with the essential information ('List the versions'), making it efficient and easy to parse. Every word earns its place with zero redundancy.

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?

Given the tool's complexity (9 parameters, no annotations, no output schema), the description is insufficient. It doesn't address authentication requirements, pagination behavior, error conditions, or relationship to sibling tools. For a list operation in a family of script project tools, more context about what 'versions' represent and how this fits into the broader workflow would be helpful.

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 9 parameters. The description adds no parameter-specific information beyond what's in the schema (e.g., it doesn't explain how scriptId is obtained or typical pageSize values). With high schema coverage, the baseline score of 3 is appropriate as the description doesn't enhance parameter understanding but doesn't need to compensate for schema gaps.

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 clearly states the verb ('List') and resource ('versions of a Google Apps Script project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'script_projects_deployments_list' or 'script_projects_versions_get', which could cause confusion about when to use this specific list operation versus other list or get operations.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'script_projects_versions_get' (for a single version) and 'script_projects_deployments_list' (for deployments), the agent lacks context about when this list operation is appropriate versus other retrieval methods. No exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mohalmah/google-appscript-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server