Skip to main content
Glama
CapyKkuing

naver-mail-mcp

by CapyKkuing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_threads

Read-only

Find email threads in Naver Mail by query and page through results to get thread IDs for full reading or follow-up actions. Results are previews only; use thread IDs to open complete conversations.

Instructions

IMPORTANT: results are previews (up to 5 messages per thread, from this page only). Never answer questions about the latest or unread email from previews alone; call get_thread to read relevant threads in full. Lists email threads in the Naver Mail account matching a query, newest first, with pagination. Each thread has its id, messageCount (messages from this page) and messages with id, sender, recipients, date, labelIds, subject and snippet. Use it to find thread ids before reading full threads or acting on emails.

Input Schema

NameRequiredDescriptionDefault
viewNoTHREAD_VIEW_MINIMAL (default) includes subject and snippet; THREAD_VIEW_METADATA_ONLY excludes them.
queryNoGmail search syntax, converted to IMAP for Naver Mail. Supported: from:, to:, cc:, bcc:, subject:, "exact phrase", bare keywords, after:YYYY/MM/DD (inclusive), before:YYYY/MM/DD (exclusive), newer_than:/older_than: (e.g. 7d, 2m, 1y), is:unread, is:read, is:starred, has:attachment, filename:, larger:/smaller: (e.g. 5M), in:inbox|sent|trash|spam|draft|anywhere, label:<folder name>, OR, { }, -exclude, ( ). Bare keywords match subject, sender or body. has:attachment/filename: check message structure of the newest 3000 messages per folder (add a date filter for older mail). Default scope: all folders except trash, spam and drafts. Unsupported operators (category:, AROUND …) are ignored and reported in warnings. Prefer short keyword queries.
pageSizeNoMax messages to return (grouped into threads). Default 20, max 50.
pageTokenNonextPageToken from a previous call.
includeTrashNoInclude messages in Trash. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint, but the description adds critical behavior beyond them: results are previews capped at 5 messages per thread, scoped to the current page, and messageCount reflects only this page. That caveat materially changes how an agent should interpret and trust the output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical preview warning is front-loaded before the purpose statement, which is the right priority ordering. Slightly redundant, since the closing sentence repeats the "read full threads" advice already given in the opening warning, but no sentence is wasted.

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?

No output schema exists, yet the description spells out the shape of each thread and message, so an agent knows what it receives. Combined with the preview limitation and the get_thread escalation path, nothing needed to call this correctly is missing.

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%, and the query syntax, view enum, pageSize bounds and pageToken meaning are all fully documented in the schema. The description only restates "with pagination" and preview semantics, adding little parameter-level meaning beyond structured fields.

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 ("Lists email threads in the Naver Mail account matching a query"), plus ordering (newest first) and pagination. It also enumerates the returned fields (id, messageCount, messages with sender/recipients/date/labelIds/subject/snippet), which makes it easy to distinguish from get_thread.

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 says "Use it to find thread ids before reading full threads or acting on emails" and names the alternative (get_thread) with the condition that selects it. It also gives a when-not rule: never answer questions about the latest or unread email from previews alone.

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