Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_get_labels

Lists all labels for a Gmail account so you can identify and organize messages by label.

Instructions

List all labels for an email account (Gmail only)

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": {
      "accountId": "<accountId>"
    },
    "name": "email_get_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. "List" implies a read-only operation and the Gmail-only restriction adds useful scope, but the description does not mention authentication requirements, pagination, return shape, or whether disabled/system labels are included.

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 front-loaded sentence with no wasted wording. The operation, resource, and Gmail-only constraint are all stated immediately.

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 simple one-parameter read tool, the description adequately conveys the core action and platform scope. The main gap is the undocumented accountId semantics, which matters because the schema provides no parameter description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required accountId parameter with 0% schema description coverage, so the description must compensate. Saying "for an email account" implies that accountId identifies the target account, but it does not explain the expected ID format or how to obtain a valid account ID.

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 gives a specific verb and resource: "List all labels for an email account." It also narrows the provider scope with "(Gmail only)." It does not explicitly distinguish itself from similarly named siblings such as email_label or email_get_categories, so it is clear but not fully differentiated.

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?

The Gmail-only parenthetical gives one clear usage constraint, implicitly excluding non-Gmail accounts. However, the description does not state when to use this tool instead of related label or category tools, nor does it mention prerequisites such as account setup.

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