Skip to main content
Glama

graph_list_mail_folders

List mail folders with unread and total counts, then use the returned folder IDs to read or move messages.

Instructions

List mail folders, including their unread and total counts.

Use the returned folder IDs with graph_list_mail or graph_move_mail.

Args: parent_folder_id: Parent folder ID. Empty lists top-level folders. top: Maximum number of folders to return (default 25). skip: Number of items to skip before returning results (default 0). Graph returns at most 50 per call, so page by raising skip in steps of top. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list). mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "graph_list_mail_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
mailboxNo
next_linkNo
parent_folder_idNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations at all, the description carries the full burden and does so: it discloses the 50-item server cap, the paging strategy, that next_link overrides other paging args, that include_next_link changes the return shape to {items, next_link} versus a bare list, and that non-empty mailbox requires delegated Mail.*.Shared permissions.

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?

Front-loaded with purpose, then a compact Args block where each line adds real semantics. Minor waste in restating schema defaults (25, 0, false) verbatim, but the accompanying rationale justifies most of that repetition.

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, so the description must explain returns, and it does (counts per folder, bare list vs {items, next_link} wrapper). Paging, permissions, and mailbox scoping are all covered, leaving nothing an agent needs missing for a six-parameter list call.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it documents all six parameters with meaning beyond the schema: empty parent_folder_id means top-level, empty mailbox means own mailbox, top/skip interplay for paging, next_link precedence, and the include_next_link output-shape toggle.

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 ("List mail folders") plus the payload enrichment ("including their unread and total counts"), which distinguishes it from graph_list_mail and graph_list_contact_folders without needing the schema.

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

Usage Guidelines4/5

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

Gives explicit downstream routing: returned folder IDs feed graph_list_mail or graph_move_mail, which tells the agent this tool's role as a prerequisite in the mail workflow. It stops short of stating when-not to use it or naming a competing sibling, so it is clear context rather than full when/when-not guidance.

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