Skip to main content
Glama

create_script_project_tool

Create new Google Apps Script projects, either standalone or bound to Google Docs, Sheets, Forms, or Slides for document-specific automation.

Instructions

Create a new Apps Script project (standalone or bound to a document).

Args: title: Project title parent_id: Optional - the Google Drive ID of a container document to bind to. Leave empty for standalone scripts.

           To create a BOUND script, pass the ID of:
           - Google Sheet (from the URL: docs.google.com/spreadsheets/d/{ID}/edit)
           - Google Doc (from the URL: docs.google.com/document/d/{ID}/edit)
           - Google Form (from the URL: docs.google.com/forms/d/{ID}/edit)
           - Google Slides (from the URL: docs.google.com/presentation/d/{ID}/edit)

           Bound scripts can use document-specific features like custom menus,
           onOpen triggers, and getActiveSpreadsheet().

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
parent_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by explaining the two creation modes (standalone/bound) and the capabilities of bound scripts (custom menus, triggers, getActiveSpreadsheet()). However, it doesn't mention authentication requirements, rate limits, or error conditions that would be helpful 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear opening statement followed by parameter documentation. While slightly longer than minimal, every sentence adds value: the first establishes purpose, the parameter section provides essential usage details, and the final sentence explains bound script capabilities.

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

Completeness4/5

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

For a mutation tool with no annotations, the description provides good coverage of purpose, parameters, and usage context. The existence of an output schema reduces the need to describe return values. However, it could better address behavioral aspects like permissions or error handling given it's a creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by providing detailed semantic information for both parameters: it explains that 'title' is the project title, and 'parent_id' is optional for binding to specific Google document types, with clear examples of valid IDs and the consequences of leaving it empty.

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 specific action ('Create a new Apps Script project') and distinguishes between two resource types (standalone or bound to a document). It differentiates from sibling tools like create_doc_tool or create_spreadsheet_tool by focusing specifically on Apps Script projects, not general document creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool vs alternatives: it explains when to create standalone vs bound scripts, specifies which document types can be bound, and mentions that bound scripts enable document-specific features. This gives clear context for choosing between the two modes.

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/sam-ent/appscript-mcp'

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