Skip to main content
Glama
Sign In
mailpouch

mailpouch

by chandshy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Emails by Label

get_emails_by_label
Read-only

Retrieve emails associated with a specific label. Use optional limit and cursor to paginate through results.

Instructions

Legacy convenience wrapper for get_emails with folder set to Labels/. Prefer get_emails when you need the canonical pagination and summaryOnly options.

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": {
      "label": "<label>"
    },
    "name": "get_emails_by_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYesLabel name without prefix (e.g. Work)
limitNoEmails per page, 1-200
cursorNoOpaque cursor from previous response
account_idNoOptional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).

Output Schema

NameRequiredDescriptionDefault
countYes
emailsYes
folderYes
nextCursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.0
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Optional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).",
+  "type": "string"
+}
  2. First observedv3.0.77

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the behavioral safety profile. The description adds context of being a legacy wrapper, which is useful but does not disclose additional behavioral traits beyond annotations.

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?

Two concise sentences, front-loaded with purpose and guidance. Every word earns its place with no redundancy.

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

Completeness5/5

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

Given the output schema exists (not shown but indicated), the description adequately covers purpose and usage guidance. No additional context needed for this simple wrapper tool.

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 coverage is 100%, so parameters are well-documented in the schema. The description does not add extra meaning beyond what the schema provides, meeting the baseline.

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 tool is a legacy convenience wrapper for get_emails with a fixed folder set to Labels/<label>. It distinguishes itself from the sibling tool get_emails by specifying that get_emails is preferred for canonical pagination and summaryOnly options.

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

Usage Guidelines5/5

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

Explicitly advises to prefer get_emails for canonical pagination and summaryOnly, providing clear when-to-use and when-not-to-use guidance. Names the alternative tool directly.

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

Deploy Server

Other Tools