Skip to main content
Glama

list-contact-folder-contacts

Read-only

Retrieve contacts from any contact folder by providing its folder ID, overcoming the limitation of the default folder only.

Instructions

Get a contact collection from the default Contacts folder of the signed-in user (.../me/contacts), or from the specified contact folder.

💡 TIP: Lists contacts inside a specific folder. Pair with list-contact-folders to discover the folder id. Note: the existing list-outlook-contacts (GET /me/contacts) only returns contacts from the default folder — use this tool to read contacts from any folder. Supports $filter, $search='query', $orderby, $top, $select.

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.
searchNoKQL search query — wrap value in double quotes. Cannot combine with $filter.
filterNoOData filter expression. Add $count=true for advanced filters (flag/flagStatus, contains()). Cannot combine with $search.
countNoSet true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains().
orderbyNoSort expression, e.g. receivedDateTime desc
selectNoComma-separated fields to return, e.g. id,subject,from,receivedDateTime
expandNoExpand related entities
contactFolderIdYesPath parameter: contactFolderId
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 indicate readOnlyHint, destructiveHint false. The description adds behavioral context beyond annotations, such as pagination via @odata.nextLink, parameter restrictions (no $filter with $search), and the need for $count=true for advanced filters. It does not contradict annotations.

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

Conciseness5/5

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

The description is compact yet informative, front-loaded with the main purpose, followed by a concise tip block using bullet points and an emoji. Every sentence adds value without redundancy.

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?

Given the tool's complexity (12 parameters) and lack of output schema, the description covers all key aspects: source folder, pagination, filtering, search, sorting, and field selection. It provides a comprehensive guide for effective use.

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 coverage is 100%, so baseline is 3. The description adds extra semantic value with tips like 'start small with $top', 'wrap search in double quotes', and notes on incompatibility between $filter and $search, exceeding the schema's descriptions.

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 clearly states it gets contacts from a specific folder or the default folder, using specific verbs and resources. It distinguishes itself from the sibling tool list-outlook-contacts by explaining that the sibling only returns contacts from the default folder.

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

Usage Guidelines5/5

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

The description explicitly recommends pairing with list-contact-folders to discover the folder id, and compares with list-outlook-contacts to guide tool selection. It provides clear guidance on when to use each tool and includes usage tips for parameters like $top, $filter, and $search.

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/Softeria/ms-365-mcp-server'

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