Skip to main content
Glama

Delete File

delete_file

Deletes a specified file from a Google Apps Script project using its script ID and file name; the appsscript manifest cannot be removed.

Instructions

Delete one file from a project (the appsscript manifest cannot be deleted).

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": {
      "script_id": "<script_id>",
      "name": "<name>"
    },
    "name": "delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
script_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and mostly does not. It discloses one useful constraint (manifest is protected) but says nothing about permanence/irreversibility, required permissions, or what happens if the file or script_id is missing — significant gaps for a destructive mutation.

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 front-loaded sentence with no filler, and the caveat is placed where it will be read. Its brevity is close to under-specification rather than padding, which is the better failure mode.

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 no explanation, and the tool is simple with two required params. Still, for an irreversible mutation with zero annotation coverage, the definition should say more about failure modes and parameter meaning.

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%, so the description must compensate and does not: neither script_id nor name is clarified, and the distinction between a file name and a script/project id is left to inference. "From a project" is the only hint that script_id scopes the target.

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 ("Delete one file from a project") and adds a real scoping constraint (the appsscript manifest cannot be deleted). It is clearly distinguishable from siblings like write_file and get_project, though it never names an alternative deletion path.

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

Usage Guidelines3/5

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

Usage is implied by the name and the deletion verb; there is no explicit when-to-use versus when-not guidance. The one stated exclusion (manifest file) is the only boundary offered, and no alternatives are named.

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