Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

script.projects.versions.list

List versions of a script project to inspect revision history and track changes; use pageSize and pageToken to navigate large result sets.

Instructions

List the versions of a script project [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: create, get.

Input Schema

NameRequiredDescriptionDefault
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
pageSizeNo[query parameter] The maximum number of versions on each returned page. Defaults to 50.
scriptIdYes[URL path segment] The script project's Drive ID.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.
pageTokenNo[query parameter] The token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from a previous response.

Output Schema

NameRequiredDescriptionDefault
versionsNo
nextPageTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / pageSize / description
      Previous value: -"The maximum number of versions on each returned page. Defaults to 50."New value: +"[query parameter] The maximum number of versions on each returned page. Defaults to 50."
    • addedInput schema / properties / pageSize / format
      Added value: +"int32"
    • changedInput schema / properties / pageToken / description
      Previous value: -"The token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from a previous response."New value: +"[query parameter] The token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from a previous response."
    • changedInput schema / properties / scriptId / description
      Previous value: -"The script project's Drive ID."New value: +"[URL path segment] The script project's Drive ID."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "nextPageToken": {
+      "type": "string"
+    },
+    "versions": {
+      "items": {
+        "properties": {
+          "createTime": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "scriptId": {
+            "type": "string"
+          },
+          "versionNumber": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.3/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 helpfully discloses that this is an HTTP GET (a read) and describes how request bodies are built (typed flags win over the params map, or body_file). It does not mention auth requirements, rate limits, or pagination behavior, so disclosure is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening purpose clause is front-loaded, but the second sentence is largely generic boilerplate about request-body construction that is irrelevant to a GET list call, diluting focus. It could be trimmed without losing list-specific information.

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-value explanation is not required, yet the description still offers only a generic JSON return note. Combined with the absence of usage guidance, it is adequate but leaves gaps for an agent choosing among the version operations.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents every parameter. The description adds the merge-precedence rule (typed params win over `params`) and body_file behavior, but that duplicates what the schema descriptions already state, so baseline 3 is appropriate.

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+resource ("List the versions of a script project") and names the HTTP method, which is more than the name alone conveys. It lists the sibling operations (create, get) over the same resource but does not differentiate what each does, so an agent gets clear purpose but not full sibling disambiguation.

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?

The description names the sibling operations (create, get) but does not state when to pick this list operation vs. those alternatives or any preconditions. Usage is only implied by "List the versions of a script project."

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

Deploy Server

Other Tools