Skip to main content
Glama
Sign In
Google Workspace MCP VE

Google Workspace MCP VE

by HuntsDesk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

manage_deployment

Create, update, or delete Apps Script deployments. Create action automatically generates a new version. Requires script.deployments OAuth scope.

Instructions

Create, update, or delete an Apps Script deployment.

Side effects: create first generates a new version then deploys it (two API calls atomically); delete is destructive. To list existing deployments use list_deployments. For executing code via the API use run_script_function. Requires the script.deployments OAuth scope.

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>",
      "action": "<action>",
      "script_id": "<script_id>"
    },
    "name": "manage_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
actionYes"create", "update", or "delete".
script_idYesTarget project ID.
deployment_idNoExisting deployment ID. Required for update and delete (get from list_deployments).
descriptionNoDeployment description shown in the Apps Script UI. Required for create and update.
version_descriptionNoFor create only — description attached to the auto-created version. Defaults to `description` when omitted.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.0.0
    • changedInput schema / properties / action / description
      Previous value: -"Action to perform - \"create\", \"update\", or \"delete\""New value: +"\"create\", \"update\", or \"delete\"."
    • changedInput schema / properties / deployment_id / description
      Previous value: -"The deployment ID (required for update and delete)"New value: +"Existing deployment ID. Required for update and\ndelete (get from list_deployments)."
    • changedInput schema / properties / description / description
      Previous value: -"Deployment description (required for create and update)"New value: +"Deployment description shown in the Apps Script UI.\nRequired for create and update."
    • changedInput schema / properties / script_id / description
      Previous value: -"The script project ID"New value: +"Target project ID."
    • changedInput schema / properties / user_google_email / description
      Previous value: -"User's email address"New value: +"The user's Google email address (authenticated\naccount)."
    • changedInput schema / properties / version_description / description
      Previous value: -"Optional version description (for create only)"New value: +"For create only — description attached to\nthe auto-created version. Defaults to `description` when\nomitted."
  2. First observedv1.19.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully covers behavioral traits: side effects of create (two API calls atomically) and destructiveness of delete. It also discloses the OAuth scope requirement, going beyond what the schema provides.

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 concise (4 sentences) and front-loaded: first sentence states purpose, second covers side effects, third gives alternatives, fourth notes OAuth. No superfluous words.

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

Completeness5/5

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

Given the complexity (CRUD with side effects and OAuth), the description covers purpose, side effects, alternatives, and authorization. Input schema handles parameters, and an output schema exists (per context), so return values are covered. The description is complete.

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 coverage is 100% with clear descriptions for each parameter. The tool description adds no additional parameter-level meaning, so baseline 3 is appropriate.

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 'Create, update, or delete an Apps Script deployment', providing a specific verb and resource. It distinguishes itself from siblings by explicitly naming list_deployments for listing and run_script_function for execution.

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 tells when to use this tool (for CRUD operations on deployments) and when not to (listing via list_deployments, code execution via run_script_function). It also mentions the required OAuth scope, providing clear guidance.

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

Deploy Server

Other Tools