Skip to main content
Glama
gmail-mcp
by gchallen

get_label

Read-only

Retrieve a single Gmail label by ID or exact name, including its total and unread message and thread counts.

Instructions

One label with its message and thread counts (total and unread).

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": {
      "labelId": "<labelId>"
    },
    "name": "get_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelIdYesLabel ID or exact name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds genuinely new context by disclosing what the response contains — message and thread counts, split into total and unread — which is useful since no output schema exists. It says nothing about behavior when the label ID is unknown or whether the name lookup is case-sensitive.

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?

A single short sentence with no filler, and the most useful fact (counts included) is placed early. It is arguably over-compressed — a leading verb would cost two words and remove ambiguity — but nothing is wasted.

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?

For a one-parameter read tool with full schema coverage and complete annotations, the description is adequate: it names the resource and sketches the return payload. It stops short of the completeness a no-output-schema tool could benefit from, leaving the exact shape of the counts object and error behavior unspecified.

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%, and the single parameter is documented as "Label ID or exact name." The description adds no additional meaning about the accepted identifier forms, so the schema carries the full parameter burden and the baseline of 3 applies.

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 identifies a single specific resource ("One label") and enumerates the data it carries (message and thread counts, total and unread), which implicitly separates it from a listing tool like list_labels. It lacks an explicit verb such as "retrieve" or "fetch", so the agent must infer the operation from the noun phrase, but the resource and scope are unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus list_labels, update_label, or delete_label, and no stated preconditions. The singular "One label" hints that this is a single-item lookup, but that is inference rather than instruction, and no exclusions are offered.

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