Skip to main content
Glama

list_emails

Retrieve emails from Outlook inbox with filtering, search, pagination, and ordering options.

Instructions

List emails from Outlook inbox

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": "list_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoNumber of emails to retrieve (default: 10)
skipNoNumber of emails to skip (for pagination)
filterNoOData filter query (e.g., "isRead eq false")
searchNoSearch query to find emails
orderByNoOrder by field (e.g., "receivedDateTime DESC")receivedDateTime DESC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure and provides almost none. It does not state that this is a read-only operation, that results default to the 10 most recent emails, that it can be paginated, or what the response shape looks like.

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?

One short, front-loaded sentence with zero filler or redundancy. It is efficient, though the brevity comes at the cost of under-specification rather than being paired with adequate detail.

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

Completeness2/5

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

For a tool with five optional parameters, no annotations, and no output schema, the description is too thin. Ordering defaults, pagination semantics, read-only nature, and authentication expectations are all undocumented, leaving the agent to rely entirely on the schema for behavior.

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%, so all five parameters (top, skip, filter, search, orderBy) are already documented with defaults and examples in the schema. The description adds no additional meaning, so the baseline of 3 applies.

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?

The description states a specific verb and resource ('List emails') plus a scope ('Outlook inbox'), so an agent knows exactly what the tool returns. It does not distinguish itself from the sibling 'search_emails', which is notable given the schema also exposes a 'search' parameter.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives such as 'search_emails' or 'get_email'. The overlap between this tool's 'search' parameter and a dedicated search sibling is left entirely for the agent to guess.

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