Skip to main content
Glama

Get Project

get_project

Retrieve a standalone Apps Script project's title and every file's full source using its script_id from the editor URL.

Instructions

Get a standalone project's title and every file with its full source. script_id is the ID in the editor URL (script.google.com/d//edit).

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": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
script_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool returns a project title and every file's full source, implying a read operation, but it does not mention permission requirements, error behavior, or whether large projects may return substantial output.

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 two concise sentences with no filler. The retrieval behavior is front-loaded, and the second sentence directly clarifies the required parameter.

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

Completeness4/5

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

For a simple one-parameter getter with an output schema, the description covers the operation, the returned content, and how to obtain the required ID. The main remaining gap is lack of guidance on when to use this versus list_projects or other siblings.

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

Parameters5/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 explain the only parameter. It does so effectively by specifying that `script_id` is the ID in the editor URL and even provides the URL pattern `script.google.com/d/<id>/edit`.

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 states a specific verb and resource: 'Get a standalone project's title and every file with its full source.' It clearly defines what is retrieved, though it does not explicitly differentiate this from sibling tools such as list_projects.

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 description: use this to retrieve a project's title and all files with full source. There is no explicit when-to-use/when-not guidance or named alternative for listing projects versus fetching a single project.

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