Unified Apps Script MCP

apps_script_get_project

Read-onlyIdempotent

Retrieve metadata for any Google Apps Script project by script ID, including title, timezone, and runtime version.

Instructions

Get Apps Script project metadata.

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>"
    },
    "name": "apps_script_get_project"
  }
}

Input Schema

Name	Required	Description	Default
`scriptId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already mark the call as readOnly, idempotent, and non-destructive, so the safety profile is clear. The description adds no further behavioral detail (e.g., return shape or side effects) but does not contradict the annotations.

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?

A single, complete sentence with no filler. The key action and object are front-loaded, making the description maximally concise.

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?

No output schema exists, so the description should explain what metadata is returned; 'metadata' is vague. There is also no information about auth prerequisites or edge cases, leaving meaningful gaps for a tool called by an agent.

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 description adds no meaning beyond the param name scriptId. While minLength is the only constraint, the description does not explain what the scriptId represents or how to obtain it.

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 uses a specific verb and resource: 'Get Apps Script project metadata' clearly identifies the operation. It is not a tautology, but it doesn't explicitly differentiate from sibling tools like apps_script_get_content or apps_script_get_metrics.

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 is provided for when to use this tool versus sibling tools such as apps_script_get_content or drive_list_apps_script_projects. The agent is left to infer the appropriate selection from the tool name alone.

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