grr

Overview Schema Source Related Servers Discussions Admin

gmail.users.labels.get

Retrieve a specific Gmail label by ID to inspect its properties, type, and settings for a user.

Instructions

Gets the specified label. For more information, see Manage labels [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, delete, list, patch, update.

Input Schema

Name	Required	Description	Default
`id`	Yes	[URL path segment] The ID of the label to retrieve.
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`userId`	Yes	[URL path segment] The user's email address. The special value `me` can be used to indicate the authenticated user.	me
`dry_run`	No	Return the request that would be sent, without sending it.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`type`	No
`color`	No
`threadsTotal`	No
`messagesTotal`	No
`threadsUnread`	No
`messagesUnread`	No
`labelListVisibility`	No
`messageListVisibility`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 26, 2026

changedInput schema / properties / id / description

Previous value: -"The ID of the label to retrieve."New value: +"[URL path segment] The ID of the label to retrieve."

addedInput schema / properties / userId / default
```
Added value: +"me"
```

changedInput schema / properties / userId / description

Previous value: -"The user's email address. The special value `me` can be used to indicate the authenticated user."New value: +"[URL path segment] The user's email address. The special value `me` can be used to indicate the authenticated user."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "color": {
+      "properties": {
+        "backgroundColor": {
+          "type": "string"
+        },
+        "textColor": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "id": {
+      "type": "string"
+    },
+    "labelListVisibility": {
+      "enum": [
+        "labelShow",
+        "labelShowIfUnread",
+        "labelHide"
+      ],
+      "type": "string"
+    },
+    "messageListVisibility": {
+      "enum": [
+        "show",
+        "hide"
+      ],
+      "type": "string"
+    },
+    "messagesTotal": {
+      "type": "integer"
+    },
+    "messagesUnread": {
+      "type": "integer"
+    },
+    "name": {
+      "type": "string"
+    },
+    "threadsTotal": {
+      "type": "integer"
+    },
+    "threadsUnread": {
+      "type": "integer"
+    },
+    "type": {
+      "enum": [
+        "system",
+        "user"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does indicate a safe read via 'Gets' and '[HTTP GET]', and states that the resource is returned as JSON. It does not mention authentication requirements or error behavior, and the body_file/body-building sentence is generic boilerplate for a GET.

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

Conciseness4/5

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

The definition is front-loaded with the purpose and sibling context. The sentence about request bodies being built from typed parameters or body_file is largely irrelevant for a GET and slightly distracts, but the rest is efficient.

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 read operation with an output schema and full parameter descriptions, the description is largely complete: it explains retrieval, confirms JSON output, and distinguishes related operations. It could be improved by noting that a label ID is required and how to obtain it.

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 input schema already documents userId, id, query, params, dry_run, and body_file. The description adds no parameter-specific semantics beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb and resource: 'Gets the specified label.' It also names the sibling operations over the same resource (create, delete, list, patch, update), making the retrieval purpose clear without opening other tools.

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?

The description distinguishes this tool from its direct siblings by listing create, delete, list, patch, and update, so the agent can infer this is the read-one operation. However, it does not explicitly say when to use get versus list, such as using list to discover label IDs.

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

Deploy Server