Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

sheets.spreadsheets.developerMetadata.get

Retrieve a specific developer metadata entry from a Google Sheets spreadsheet by supplying the spreadsheet ID and metadata ID.

Instructions

Returns the developer metadata with the specified ID. The caller must specify the spreadsheet ID and the developer metadata's unique metadataId. For more information, see Read, write, and search metadata [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: search.

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.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.
metadataIdYes[URL path segment] The ID of the developer metadata to retrieve.
spreadsheetIdYes[URL path segment] The ID of the spreadsheet to retrieve metadata from.

Output Schema

NameRequiredDescriptionDefault
locationNo
metadataIdNo
visibilityNo
metadataKeyNo
metadataValueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / metadataId / description
      Previous value: -"The ID of the developer metadata to retrieve."New value: +"[URL path segment] The ID of the developer metadata to retrieve."
    • addedInput schema / properties / metadataId / format
      Added value: +"int32"
    • changedInput schema / properties / spreadsheetId / description
      Previous value: -"The ID of the spreadsheet to retrieve metadata from."New value: +"[URL path segment] The ID of the spreadsheet to retrieve metadata from."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "location": {
+      "properties": {
+        "dimensionRange": {
+          "properties": {
+            "dimension": {
+              "enum": [
+                "DIMENSION_UNSPECIFIED",
+                "ROWS",
+                "COLUMNS"
+              ],
+              "type": "string"
+            },
+            "endIndex": {
+              "type": "integer"
+            },
+            "sheetId": {
+              "type": "integer"
+            },
+            "startIndex": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "locationType": {
+          "enum": [
+            "DEVELOPER_METADATA_LOCATION_TYPE_UNSPECIFIED",
+            "ROW",
+            "COLUMN",
+            "SHEET",
+            "SPREADSHEET"
+          ],
+          "type": "string"
+        },
+        "sheetId": {
+          "type": "integer"
+        },
+        "spreadsheet": {
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "metadataId": {
+      "type": "integer"
+    },
+    "metadataKey": {
+      "type": "string"
+    },
+    "metadataValue": {
+      "type": "string"
+    },
+    "visibility": {
+      "enum": [
+        "DEVELOPER_METADATA_VISIBILITY_UNSPECIFIED",
+        "DOCUMENT",
+        "PROJECT"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully states that this is an HTTP GET and returns the resource as JSON, but it does not cover permissions, error behavior when the metadata ID is missing, or visibility constraints.

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 purpose is front-loaded and the sibling reference is useful, but the generic request-body construction sentence is largely irrelevant for a GET operation and adds noise. The description is not excessively long, but not every sentence earns its place.

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?

Given the output schema and 100% schema description coverage, the description provides enough context to call the tool correctly, including required IDs and return format. The main remaining gap is lack of permission or error-behavior guidance, which is relatively minor for this simple read operation.

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 parameter schema already documents spreadsheetId, metadataId, and the request-building fields. The description restates that spreadsheetId and metadataId are required but adds no additional parameter meaning beyond the 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?

The description states a specific verb ('Returns'), resource ('developer metadata with the specified ID'), and names the related sibling operation ('search'). An agent can distinguish this get-by-ID operation from search without opening the schema.

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 requirement to supply spreadsheetId and metadataId implies the tool should be used when the metadata ID is already known, and it mentions the sibling 'search'. However, it does not explicitly say when to use search instead or articulate a clear decision rule between the two.

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