Skip to main content
Glama

update_language

Change the display language in Gmail by specifying an RFC 3066 language tag to customize the interface for different regions or preferences.

Instructions

Updates language settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
displayLanguageYesThe language to display Gmail in, formatted as an RFC 3066 Language Tag

Implementation Reference

  • Handler function for the update_language tool that validates credentials via handleTool and calls the Gmail API to update the user's language settings.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.settings.updateLanguage({ userId: 'me', requestBody: params })
        return formatResponse(data)
      })
    }
  • Zod input schema defining the displayLanguage parameter for the update_language tool.
    {
      displayLanguage: z.string().describe("The language to display Gmail in, formatted as an RFC 3066 Language Tag")
    },
  • src/index.ts:902-913 (registration)
    Registration of the update_language tool on the MCP server, including description, schema, and handler.
    server.tool("update_language",
      "Updates language settings",
      {
        displayLanguage: z.string().describe("The language to display Gmail in, formatted as an RFC 3066 Language Tag")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.updateLanguage({ userId: 'me', requestBody: params })
          return formatResponse(data)
        })
      }
    )
  • Shared helper function used by update_language (and other tools) to handle OAuth2 authentication, client creation, and execution of Gmail API calls.
    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}`
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Updates language settings' implies a mutation operation, but it doesn't specify required permissions, whether changes are reversible, rate limits, or what the response looks like (e.g., success/failure indicators). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 extremely concise with 'Updates language settings', a single sentence that front-loads the core action and resource. There is no wasted verbiage or redundancy, making it efficient and easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a mutation tool with no annotations, no output schema, and a simple parameter, the description is incomplete. It lacks behavioral context (e.g., effects, permissions), usage guidelines, and any mention of return values or error handling. While the parameter is well-documented in the schema, the overall context for safe and effective use is insufficient.

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?

The input schema has 100% description coverage, with 'displayLanguage' documented as 'The language to display Gmail in, formatted as an RFC 3066 Language Tag'. The description adds no additional parameter details beyond what the schema provides, such as examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't need to heavily.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Updates language settings' clearly states the action (update) and resource (language settings), making the purpose understandable. However, it's somewhat vague about what specifically gets updated (e.g., Gmail display language vs. system-wide settings) and doesn't differentiate from potential siblings like 'get_language' beyond the verb difference. It avoids tautology but lacks specificity.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing 'get_language' first), exclusions, or compare it to similar tools like 'update_label' or 'update_vacation' in the sibling list. Usage is implied by the verb 'updates' but lacks explicit context.

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