Skip to main content
Glama

get_version

Retrieve metadata for a specific version of a Google Apps Script project, including its description and creation time.

Instructions

Fetch metadata for a specific immutable version of a Google Apps Script project.

A "version" in Apps Script is a snapshot of script code taken at a point in time — versions are referenced by deployments and cannot be edited after creation. Use this to inspect the description/create-time of one known version. For the full list of versions on a project, use list_versions. To create a new version from the current code, use create_version. To inspect deployments that point to versions, use list_deployments.

Requires OAuth scope: https://www.googleapis.com/auth/script.projects.readonly (read-only) or the broader script.projects scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesUser's email address. Required.
script_idYesThe Apps Script project ID — the string after `/d/` in the `script.google.com/home/projects/<id>` URL, or the `scriptId` field returned by `create_script_project` / `list_script_projects`.
version_numberYesThe 1-indexed integer version number to retrieve (1 for the first version, 2 for the second, etc.). Must refer to an already-created version; requesting a non-existent number raises a `404 Not Found` handled by the error decorator.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, but description notes immutability (cannot be edited), error on non-existent version (404), and required OAuth scope. Could mention that it only returns metadata, not code.

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?

Few sentences, well-structured with bullet points for alternatives. Every sentence adds value without redundancy.

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?

Output schema exists, so return values not needed. Description covers purpose, usage, prerequisites, alternatives, and error behavior—complete for a metadata retrieval tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with good parameter descriptions. Description adds value by explaining version concept, 1-indexing of version_number, and error handling, going 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 'Fetch metadata for a specific immutable version', with verb and resource. It differentiates from siblings like list_versions, create_version, and list_deployments.

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?

Explicitly tells when to use this tool ('inspect the description/create-time of one known version') and when to use alternatives (list_versions, create_version, list_deployments).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HuntsDesk/ve-gws'

If you have feedback or need assistance with the MCP directory API, please join our Discord server