Skip to main content
Glama

graph_list_message_rules

List inbox rules for your mailbox or a shared mailbox, showing conditions, actions, and rule order so you can review how incoming email is handled.

Instructions

List the inbox rules, including their conditions, actions, and order.

Args: 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_message_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that results include conditions, actions, and ordering, and that shared-mailbox access needs delegated Mail.*.Shared permissions — meaningful context beyond the schema. It does not disclose pagination, result limits, or whether the operation fails without those 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?

The purpose sentence is front-loaded and the Args block is compact and skimmable. Slight redundancy in restating the permission requirement inside the parameter note, but nothing wasted.

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

Completeness4/5

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

For a one-optional-parameter read tool with no output schema and no annotations, the description covers purpose, return contents, the empty-default behavior, and the permission prerequisite. Only pagination/volume behavior is missing, which is minor at this complexity.

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 0% for the single optional 'mailbox' parameter, so the description has to compensate. It does explain the empty-string default (own mailbox), the accepted value type (address or user ID), and the permission implication, which is genuinely useful, but it does not clarify format expectations or error behavior for an invalid mailbox.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List the inbox rules") and adds the scope of what is returned (conditions, actions, order), which clearly separates it from the create/delete/update message-rule siblings. It stops short of explicitly naming an alternative, so it is clear but not maximally differentiated.

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

Usage Guidelines3/5

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

The Args block gives real usage context — leave mailbox empty to target your own mailbox, or supply a shared address/user ID which requires delegated Mail.*.Shared permissions. There is no explicit when-to-use versus when-not-to-use guidance, and no mention of what to do if you only want a single rule.

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