Skip to main content
Glama
kharonx
by kharonx

list-shared-mailbox-folder-messages

list-shared-mailbox-folder-messages
Read-onlyIdempotent

Retrieve messages from a specific folder in a shared mailbox. Supports filters, full-text search, time ranges, and pagination for targeted message lookup.

Instructions

List/search messages inside a folder of a shared mailbox.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd of explicit time range (ISO date or datetime)
fromNoStart of explicit time range (ISO date or datetime, overrides timeRange)
cursorNoContinuation token (nextCursor of a previous truncated response). Continues that listing; other query inputs are ignored.
filterNoOData $filter expression, e.g. "importance eq 'high'" or "hasAttachments eq true"
searchNoFull-text search (KQL supported), e.g. 'from:kiss.peter@ceg.hu subject:"AI projekt" hasattachment:true'
selectNoComma separated list of properties to return (OData $select)
mailboxYesShared mailbox address
orderbyNoOData $orderby, e.g. "receivedDateTime desc"
folderIdYesMail folder id
maxItemsNoMaximum items to return across pages (default 50, max 500). Pagination via @odata.nextLink is handled automatically; when the result is truncated, pass its nextCursor as cursor to continue.
timeRangeNoNamed time range applied on receivedDateTime
Install Server

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. However, the description adds no behavioral detail beyond what the name and schema already convey—no mention of pagination, default ordering, or how search/filter interactions behave. There is no contradiction, but also no added transparency.

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 a single front-loaded sentence with no filler: 'List/search messages inside a folder of a shared mailbox.' It is appropriately compact, though slightly too thin to earn a 5 by missing any routing or contextual detail.

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

Completeness3/5

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

Given the tool's complexity (11 parameters, cursor pagination, search/filter modes), the one-sentence description is minimal. The schema carries the parameter details, but the description does not not guide an agent on when to use this vs list-shared-mailbox-messages or how to obtain the required folderId (e.g., via list-shared-mailbox-folders). Adequate but with clear contextual gaps.

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 11 parameters—including cursor, maxItems, timeRange, and search—are documented in the input schema. The description itself adds no parameter-level meaning, but with full schema coverage the baseline of 3 is appropriate.

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 states a specific verb ('List/search') and resource ('messages inside a folder of a shared mailbox'), which clearly distinguishes it from siblings like list-shared-mailbox-messages (all shared-mailbox messages) and list-mail-folder-messages (non-shared mailbox). This leaves little ambiguity about the tool's scope.

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 description implies usage for messages inside a specific folder of a shared mailbox, but gives no explicit guidance about when to choose it over alternatives. Sibling names offer context, but the tool itself does not state exclusions or name the more general shared-mailbox listing tool.

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

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/kharonx/mcp_gateway'

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