Skip to main content
Glama

list-outlook-contacts

list-outlook-contacts
Read-only

Retrieve contacts from the signed-in user's default Outlook contacts folder, with support for filtering, searching, and pagination.

Instructions

Get a contact collection from the default contacts folder of the signed-in user. There are two scenarios where an app can get contacts in another user's contact folder:

💡 TIP: $filter only supports startswith() — contains() and eq on emailAddresses do not work. Use $search as alternative for broader matching.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoPage size (Graph $top). Start small (e.g. 5–15) so responses fit the model context; raise only if needed. Use $select to return fewer fields per item. For more rows, use @odata.nextLink from the response instead of a very large $top.
skipNoItems to skip for pagination. Not supported with $search.
countNoSet true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains().
expandNoNavigation properties to inline, e.g. attachments on a message or event. Only navigation properties can be expanded: expanding a non-navigation property such as a message body fails with "Parsing OData Select and Expand failed", and an unsupported value may be ignored rather than reported. Request ordinary fields with $select instead.
filterNoOData filter expression. Add $count=true for advanced filters (flag/flagStatus, contains()). Cannot combine with $search.
searchNoKQL search query — wrap value in double quotes. Cannot combine with $filter.
selectNoComma-separated fields to return, e.g. id,subject,from,receivedDateTime
orderbyNoSort expression, e.g. receivedDateTime desc
fetchAllPagesNoFollow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a small $top first, then paginate or narrow with $filter/$search.
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
Behavior4/5

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

Annotations declare readOnlyHint: true and destructiveHint: false, and the description's 'Get' operation is consistent (no contradiction). Beyond annotations, the description adds a valuable behavioral detail: the $filter limitation (only startswith() supported for this endpoint) and the $search alternative, which is non-obvious Graph API behavior an agent would not infer from the schema. Pagination behavior is referenced implicitly through parameters but not described in the tool text, though annotations carry the safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence, and the tip is useful. However, the sentence 'There are two scenarios where an app can get contacts in another user's contact folder:' is clearly truncated—it introduces content that never materializes, which is confusing and wastes space. The description is short but completeness suffers from this dangling clause.

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?

For a read-only list tool with 11 optional parameters and no output schema, the description covers the primary purpose and provides a key filtering tip, but the unfinished 'two scenarios' sentence leaves a meaningful contextual gap. It doesn't describe the response shape, which given no output schema would be helpful (though the parameter docs mitigate this). The pagination and safety aspects are reasonably handled via schema and annotations. Decent but incomplete due to the truncation.

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 description coverage is 100% with detailed parameter docs (e.g., top explains context-window considerations, fetchAllPages warns about enormous payloads, count explains ConsistencyLevel). The description's tip adds meaning about filter/search semantics beyond the schema—specifically that contains()/eq on emailAddresses fail and $search is the alternative—which directly informs how to use those parameters. This extra nuance elevates it above the baseline 3.

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 ('Get') with a clear resource ('contact collection') scoped to 'the default contacts folder of the signed-in user,' which distinguishes it from siblings like list-contact-folder-contacts (specific folder) and get-outlook-contact (single contact). The tip about $filter and $search further clarifies its filtering capabilities. Purpose is unambiguous and distinct from sibling tools.

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 TIP provides practical guidance on when to use $filter vs $search (startswith() works, contains()/eq on emailAddresses don't; use $search for broader matching). However, the truncated sentence 'There are two scenarios where an app can get contacts in another user's contact folder:' never completes, leaving a gap. It also doesn't explicitly differentiate from siblings like list-contact-folder-contacts or state when NOT to use this tool. Some use guidance exists but no alternative routing.

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/A-Impact-Pavel/ms365-mcp'

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