google-appscript-mcp-server

update_script_content

Update the content of a Google Apps Script project by providing its script ID and an array of files to replace the existing ones.

Instructions

Updates the content of a specified Google Apps Script project.

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": {
      "scriptId": "<scriptId>",
      "files": "<files>"
    },
    "name": "update_script_content"
  }
}

Input Schema

Name	Required	Description	Default
`files`	Yes	The files to be updated in the script project.
`scriptId`	Yes	The ID of the script project to update.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'updates the content' but does not reveal whether this replaces all files, requires specific permissions, is reversible, or has side effects.

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 concise sentence with no redundant or extraneous information. It is front-loaded with the key action and resource.

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 mutation tool with no annotations and no output schema, the description is thin. It does not explain whether the update is a full replacement or partial, what the response looks like, or any required permissions, leaving the agent without adequate context.

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 descriptions cover 100% of parameters (scriptId and files), and the tool description adds no additional parameter semantics. The baseline of 3 is appropriate because the schema already provides the needed meaning.

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 action ('Updates') and the target ('content of a specified Google Apps Script project'). This distinguishes it from sibling tools like script_projects_get_content (reads) and script_projects_deployments_update (updates deployments), though it could be more explicit about the involvement of files.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives such as get_content for reading or deployments_update for updating deployments, nor does it state any prerequisites or exclusions.

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