Skip to main content
Glama
marlonluo2018

Microsoft Graph MCP Server

browse_email_cache

Browse cached emails with pagination. Use page_number to navigate pages, each showing email summaries and attachment info.

Instructions

Browse emails in the cache with pagination. Returns summary information with number column indicating position in cache. Use page_number to navigate. Automatically manages browsing state with disk cache for persistence. WORKFLOW: Use search_emails to load emails into the cache first. ATTACHMENT INFO: Each email now includes attachment details (id, name, size, contentType) so you can see what attachments are available before downloading. IMAGE ATTACHMENTS: When you see image attachments (contentType starts with 'image/'), use get_email_content to retrieve them. Image content will be included automatically for multimodal analysis (requires MULTIMODAL_SUPPORTED=true). You MUST then analyze the images - they often contain critical information not mentioned in text. Returns: {current_page: integer, total_pages: integer, count: integer, total_count: integer, emails: array (with attachments array), date_range: string, filter_date_range: string, timezone: string}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoBrowsing mode. DEFAULT to 'llm' for most cases - use 'llm' when user wants you to analyze, summarize, or process emails (~20 per page for comprehensive view). Use 'user' ONLY when user EXPLICITLY requests to browse page-by-page themselves (~5 per page for human reading).llm
page_numberYesPage number to view (starts at 1)
Behavior5/5

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

With no annotations, the description fully handles transparency. It reveals the tool returns paginated summary info, manages browsing state with disk cache, and includes attachment details. It also specifies that image attachments require get_email_content for retrieval and multimodal analysis. No contradictions.

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 description is detailed but well-structured: primary function, workflow, attachment handling, return format. Each part serves a purpose without undue repetition. Minor verbosity, but overall efficient and front-loaded.

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 tool's complexity (2 parameters, no output schema), the description is remarkably complete. It provides the return structure, explains caching, attachment inclusion, and multimodal workflow. Sibling tools are appropriately referenced (search_emails, get_email_content). No gaps.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for both parameters. The description adds significant value beyond schema: explains mode enum behavior in detail (defaults, page sizes, usage contexts) and the role of page_number in navigation. The parameter semantics are well-enriched.

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 browses cached emails with pagination. It distinguishes from sibling tools like search_emails (loads cache) and get_email_content (retrieves images), making the specific function unambiguous.

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?

Explicit workflow is provided: use search_emails first. The mode parameter is explained with detailed guidance on when to use 'llm' vs 'user'. Also instructs to use get_email_content for image attachments, covering when-not-to-use and alternatives.

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/marlonluo2018/microsoft_graph_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server