Email MCP Server

Get email status

get_email_status

Read-only

Check an email's read, flag, and label state without fetching its body. Use it to verify unread or flagged messages and confirm marking actions without changing seen status.

Instructions

Get the current read/flag/label state of an email without fetching its body. Much cheaper than get_email when you only need to check whether an email is unread, flagged, or which labels it has. Also useful to confirm the result of a mark_email call. Does NOT mark the email as seen.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`account`	Yes	Account name from list_accounts
`emailId`	Yes	Email ID from list_emails or search_emails
`mailbox`	No	Mailbox path (default: INBOX)	INBOX

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`date`	Yes
`from`	Yes
`seen`	Yes
`labels`	Yes
`flagged`	Yes
`mailbox`	Yes
`subject`	Yes
`answered`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.0Oct 17, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "answered": {
+      "type": "boolean"
+    },
+    "date": {
+      "type": "string"
+    },
+    "flagged": {
+      "type": "boolean"
+    },
+    "from": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "labels": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "mailbox": {
+      "type": "string"
+    },
+    "seen": {
+      "type": "boolean"
+    },
+    "subject": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "mailbox",
+    "subject",
+    "from",
+    "date",
+    "seen",
+    "flagged",
+    "answered",
+    "labels"
+  ],
+  "type": "object"
+}

First observedv0.2.3Jul 30, 2026

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, so the safety profile is covered; the description reinforces it with 'Does NOT mark the email as seen' and adds cost context ('Much cheaper than get_email'). It discloses the no-side-effect trait clearly, though it stops short of describing caching, consistency, or rate behavior.

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?

Three short sentences, each earning its place: what it returns, why it beats get_email, and the no-side-effect guarantee. Front-loaded with the core purpose.

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?

For a read-only status tool with full schema coverage and an output schema, the description covers everything an agent needs: what state is returned, when to prefer it, and that it has no marking side effect. No material gap remains.

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 account, emailId, and mailbox are already documented in the schema. The description adds no syntax or semantics beyond that, which matches the baseline 3 when the schema does the heavy lifting.

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?

States a specific verb and resource ('Get the current read/flag/label state of an email') and explicitly scopes what it does not do ('without fetching its body'). It cleanly distinguishes itself from siblings get_email and mark_email by naming both.

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?

Names the alternative (get_email) with the selection condition ('when you only need to check whether an email is unread, flagged, or which labels it has'), and adds a second use case (confirming a mark_email result). When-to-use is explicit.

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

Deploy Server