Skip to main content
Glama

get_label

Retrieve a specific Gmail label by its unique ID to access label details for email organization and management.

Instructions

Get a specific label by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the label to retrieve

Implementation Reference

  • src/index.ts:454-465 (registration)
    Registers the MCP tool 'get_label' with input schema (id: string) and inline handler. The handler uses the shared 'handleTool' utility to authenticate, create a Gmail client, and call gmail.users.labels.get to retrieve the label by ID, then formats the response.
    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 inline handler function for the 'get_label' tool, which delegates to 'handleTool' for auth and API execution.
    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)
      })
    }
  • Input schema for 'get_label' tool using Zod: requires 'id' as string.
    {
      id: z.string().describe("The ID of the label to retrieve")
    },
  • Shared helper 'handleTool' used by 'get_label' and other tools to manage OAuth2 authentication, validate credentials, instantiate Gmail client, execute the provided API callback, and handle errors.
    const handleTool = async (queryConfig: Record<string, any> | undefined, apiCall: (gmail: gmail_v1.Gmail) => Promise<any>) => {
      try {
        const oauth2Client = queryConfig ? createOAuth2Client(queryConfig) : defaultOAuth2Client
        if (!oauth2Client) throw new Error('OAuth2 client could not be created, please check your credentials')
    
        const credentialsAreValid = await validateCredentials(oauth2Client)
        if (!credentialsAreValid) throw new Error('OAuth2 credentials are invalid, please re-authenticate')
    
        const gmailClient = queryConfig ? google.gmail({ version: 'v1', auth: oauth2Client }) : defaultGmailClient
        if (!gmailClient) throw new Error('Gmail client could not be created, please check your credentials')
    
        const result = await apiCall(gmailClient)
        return result
      } catch (error: any) {
        return `Tool execution failed: ${error.message}`
      }
    }
  • Utility to format API responses for MCP tools, used by 'get_label' handler.
    const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states a read operation ('Get') but doesn't mention permissions, rate limits, error handling, or response format. For a tool with zero annotation coverage, this is insufficient to inform the agent about behavioral traits beyond the basic action.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, achieving optimal conciseness for this simple tool.

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 low complexity (1 parameter, 100% schema coverage) but lack of annotations and output schema, the description is minimally adequate. It states what the tool does but misses behavioral context and usage guidelines. For a read operation with no output schema, more detail on response format would improve completeness.

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%, with the single parameter 'id' documented in the schema as 'The ID of the label to retrieve'. The description adds no additional meaning beyond this, such as ID format or examples. Baseline 3 is appropriate when the schema already fully describes parameters.

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 clearly states the action ('Get') and resource ('a specific label by ID'), making the purpose understandable. It distinguishes from siblings like 'list_labels' by specifying retrieval of a single item, though it doesn't explicitly name alternatives. A 5 would require explicit sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'list_labels' or 'patch_label'. The description implies usage for retrieving a known label ID but doesn't state prerequisites, exclusions, or contextual recommendations. This leaves the agent without usage direction.

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/nk900600/gmail-mcp'

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