Skip to main content
Glama

List Projects

list_projects

Lists standalone Google Apps Script projects in the user's Drive, with optional title-substring filtering; scripts bound to Sheets, Docs, or Forms are excluded.

Instructions

List standalone Apps Script projects in the user's Drive, optionally filtered by a title substring. Scripts bound to a Sheet/Doc/Form are not listed, but work with the other tools when you pass their script ID.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 burden, and it does disclose the key behavioral boundary: bound scripts are excluded from results even though other tools can still operate on them by ID. However, it says nothing about authorization scope, whether results are paginated, or how the limit interacts with total results, which leaves meaningful behavioral gaps for an unannotated tool.

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?

Two sentences, no filler, with the primary scope statement front-loaded and the exclusion caveat plus workaround following immediately. Every clause carries actionable information.

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 two-parameter read tool with an output schema (so return shape need not be described), the definition covers scope, exclusions, and the filter semantics adequately. The remaining gap is limit/pagination behavior, which an agent would need to know to retrieve more than the default page.

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 description coverage is 0%, so the description must supply parameter meaning, and it does define the intent of the query parameter as a title-substring filter, which the bare schema does not convey. It omits any explanation of the limit parameter beyond the schema's default of 50, so one of the two parameters remains unexplained.

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?

The description states a specific verb and resource ("List standalone Apps Script projects in the user's Drive") and immediately bounds the scope by excluding bound scripts, which is the main ambiguity an agent would face. It is clearly distinguishable from get_project (single fetch) and create_project (mutation) in the sibling set.

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

Usage Guidelines4/5

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

It gives a clear usage context: use this for standalone projects, and if a script is bound to a Sheet/Doc/Form, use the other tools with the script ID instead. That is a genuine routing rule, but it stops short of stating when to prefer this over a direct get_project call or how to page through large result sets.

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