google-workspace-mcp-advanced

create_deployment

Create an Apps Script deployment by specifying a script ID, version number, and description. Use dry run mode to preview changes before applying.

Instructions

Create an Apps Script deployment.

Args: user_google_email: The user's Google email address. Required. script_id: The Apps Script project ID. description: Deployment description. version_number: Version number for deployment (must be >= 1). dry_run: Preview deployment creation without mutation. Defaults to True.

Returns: str: Confirmation of preview or deployment creation.

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": {
      "user_google_email": "<user_google_email>",
      "script_id": "<script_id>",
      "description": "<description>",
      "version_number": "<version_number>"
    },
    "name": "create_deployment"
  }
}

Input Schema

Name	Required	Description	Default
`user_google_email`	Yes
`script_id`	Yes
`description`	Yes
`version_number`	Yes
`dry_run`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.10Jun 2, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations provided, so description details behavior: dry_run default creates preview, returns confirmation string, version_number must be >=1. Discloses the dry run vs actual mutation distinction.

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?

Two sentences plus args list; action is front-loaded. Some redundancy with 'Returns:' line, but overall efficient.

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?

Covers inputs and output well for a create tool. Missing prerequisites (e.g., existing script project) and auth requirements, but adequate given 5 params and output schema.

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, description thoroughly explains each parameter: user_google_email required, script_id, description, version_number constraint (>=1), dry_run default. Adds significant meaning beyond schema.

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?

Description clearly states 'Create an Apps Script deployment' with specific verb and resource, distinguishing it from sibling tools like update_deployment and delete_deployment.

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 guidance on when to use this tool versus alternatives like update_deployment or list_deployments. Missing prerequisites or context for creation.

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

Deploy Server