Skip to main content
Glama

Create Project

create_project

Creates a standalone Google Apps Script project with an empty Code file, providing a starting point for writing and running new scripts in a user's Google account.

Instructions

Create a standalone Apps Script project with an empty Code file.

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": {
      "title": "<title>"
    },
    "name": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose a genuine behavioral detail — the created project will contain exactly one empty Code file — but says nothing about authentication scopes, whether duplicate titles are rejected, or what happens if the call is repeated (non-idempotence). Those are meaningful gaps for a mutation tool with zero annotation coverage.

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?

A single short sentence with no filler, and the key information (standalone project, empty Code file) is front-loaded. Nothing is wasted, though nothing is elaborated either.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the operation is simple with one parameter. Still, the undefined title parameter and the unspecified side effects of creation leave an agent with open questions before calling.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter (title) is undocumented. The description never explains what the title controls — display name versus Drive file name, uniqueness constraints, or accepted characters — so it fails to compensate for the missing schema documentation.

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?

States a specific verb and resource ("Create a standalone Apps Script project") plus the resulting state ("with an empty Code file"), so the agent knows exactly what will exist after the call. It distinguishes the tool from siblings like get_project and list_projects by implication of creation, though it never names them explicitly.

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?

No statement of when to use this versus alternatives or prerequisites. The word "standalone" hints that this is for unbound projects rather than script files added to existing containers, but that distinction is never spelled out and no alternative tool is named.

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