Skip to main content
Glama
mohalmah

Google Apps Script MCP Server

by mohalmah

script_projects_create

Create a new Google Apps Script project by specifying a parent project ID and title for the script.

Instructions

Create a new Google Apps Script project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parentIdYesThe ID of the parent project.
titleYesThe title of the new script project.

Implementation Reference

  • The core handler function `executeFunction` that implements the tool logic: validates inputs, authenticates with OAuth, makes POST request to Google Apps Script API to create project, handles responses and errors with detailed logging.
    const executeFunction = async ({ parentId, title }) => {
      const baseUrl = 'https://script.googleapis.com';
    
      try {
        console.log('🔨 Creating new Google Apps Script project:', title);
        
        // Validate required parameters
        if (!title) {
          throw new Error('title is required');
        }
    
        const projectData = {
          title
        };
    
        // Add parentId if provided
        if (parentId) {
          projectData.parentId = parentId;
        }
    
        // Construct the URL for the API request
        const url = new URL(`${baseUrl}/v1/projects`);
        console.log('🌐 API URL:', url.toString());
    
        // Get OAuth headers
        const headers = await getAuthHeaders();
        headers['Content-Type'] = 'application/json';
        console.log('🔐 Authorization headers obtained successfully');
    
        // Perform the fetch request
        const response = await fetch(url.toString(), {
          method: 'POST',
          headers,
          body: JSON.stringify(projectData)
        });
    
        console.log('📡 API Response Status:', response.status, response.statusText);
    
        // 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(),
            error: errorData,
            timestamp: new Date().toISOString()
          };
    
          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();
        console.log('✅ Successfully created script project');
        return data;
        
      } catch (error) {
        console.error('❌ Error creating script project:', {
          message: error.message,
          stack: error.stack,
          title,
          parentId,
          timestamp: new Date().toISOString()
        });
        
        // Return detailed error information for debugging
        return { 
          error: true,
          message: error.message,
          details: {
            title,
            parentId,
            timestamp: new Date().toISOString(),
            errorType: error.name || 'Unknown'
          }
        };
      }
    };
  • The tool schema definition including name 'script_projects_create', description, input parameters schema with properties parentId and title, and required fields.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'script_projects_create',
          description: 'Create a new Google Apps Script project.',
          parameters: {
            type: 'object',
            properties: {
              parentId: {
                type: 'string',
                description: 'The ID of the parent project.'
              },
              title: {
                type: 'string',
                description: 'The title of the new script project.'
              }
            },
            required: ['parentId', 'title']
          }
        }
      }
    };
  • tools/paths.js:3-3 (registration)
    The tool file path is registered in the toolPaths array, which is used for dynamic discovery and loading of tools.
    'google-app-script-api/apps-script-api/script-projects-create.js',
  • lib/tools.js:8-64 (registration)
    The `discoverTools` function dynamically loads all tools by importing modules from paths in toolPaths, extracting apiTool, wrapping with logging, and returning the list of tools for 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 the full burden of behavioral disclosure. While 'Create' implies a write operation, the description doesn't address permissions required, whether this is idempotent, what happens on failure, or what the response contains (e.g., project ID). This leaves significant gaps for a mutation tool.

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, efficient sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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?

For a creation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after creation (e.g., returns a project ID), potential errors, or how it integrates with sibling tools. Given the complexity of script projects and the rich sibling toolset, more context is needed.

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%, with both parameters clearly documented in the schema. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline score of 3 where the schema does the heavy lifting.

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 ('Create') and resource ('new Google Apps Script project'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'script_projects_versions_create' or 'script_projects_deployments_create', which also create related resources but not the project itself.

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. It doesn't mention prerequisites (e.g., needing a parent project), when not to use it, or how it differs from sibling tools like 'script_projects_versions_create' that might be more appropriate in certain contexts.

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