Skip to main content
Glama

get_label

Retrieve a specific Gmail label by providing its ID. Access label details to organize your email workflows.

Instructions

Get a specific label by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the label to retrieve

Implementation Reference

  • src/index.ts:468-479 (registration)
    The tool 'get_label' is registered with the MCP server using server.tool(). It takes an 'id' parameter (string) describing the label ID to retrieve.
    server.tool("get_label",
      "Get a specific label by ID",
      {
        id: z.string().describe("The ID of the label to retrieve")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.labels.get({ userId: 'me', id: params.id })
          return formatResponse(data)
        })
      }
    )
  • The handler function for 'get_label' receives the Gmail client, calls gmail.users.labels.get() with the provided id, and returns the label data formatted as a JSON response.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.labels.get({ userId: 'me', id: params.id })
        return formatResponse(data)
      })
    }
  • The input schema for 'get_label' defines a single required parameter 'id' of type string, describing the ID of the label to retrieve.
    {
      id: z.string().describe("The ID of the label to retrieve")
    },
Behavior2/5

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

No annotations exist, and the description does not disclose behavioral traits such as permissions, rate limits, or side effects, leaving the agent to assume it is a simple read operation.

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?

The description is one concise sentence with no wasted words, conveying the essential information efficiently.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is minimally sufficient but lacks any background on labels or prerequisites.

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 parameter 'id' is described adequately in the schema; the tool description adds no additional 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 clearly states the action ('get'), the resource ('label'), and the selection criterion ('by ID'), effectively distinguishing it from sibling tools like list_labels or update_label.

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?

No explicit guidance on when to use this tool versus alternatives is provided, though the purpose is obvious enough for a single-resource retrieval; it could mention that list_labels retrieves all labels.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shinzo-labs/gmail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server