Skip to main content
Glama

graph_list_contact_folders

Lists contact folders and provides folder IDs for use when listing contacts, with paging controls to browse results.

Instructions

List contact folders.

Use the returned folder IDs with graph_list_contacts.

Args: top: Maximum number of folders to return (default 25, maximum 50). skip: Number of items to skip before returning results (default 0). Graph returns at most 50 per call, so page by raising skip in steps of top. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list).

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_contact_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it states the 25 default/50 cap, that Graph returns at most 50 per call, that next_link overrides other paging args, and that include_next_link switches the return shape between a bare list and {items, next_link}. It does not mention permission requirements or what a folder object contains, but the paging and response-shape behavior are unusually well covered.

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?

A one-line purpose followed by a workflow pointer and a clean Args block, with the most important scoping information front-loaded. The Args section is slightly verbose in repeating defaults that also appear in the schema, but nothing is padded or rambling.

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 four-parameter read tool with no annotations and no output schema, the description covers defaults, paging limits, override precedence, and the two possible return shapes, which is enough to call it correctly. It omits what a folder record actually contains, a minor gap given there is no output schema to fall back on.

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 0%, so the description must define all four parameters, and it does: top (default 25, max 50), skip (default 0, paging step), next_link (opaque URL, overrides paging), include_next_link (return-shape toggle). The only weakness is that the stated max of 50 for 'top' contradicts the schema's far larger numeric maximum.

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 opens with a specific verb and resource, 'List contact folders,' and immediately ties the output to the sibling graph_list_contacts, so the agent knows this is the folder-enumeration step preceding contact listing. It stops short of an explicit contrast with siblings like graph_list_mail_folders, which is why it is not a 5.

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

Usage Guidelines4/5

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

It gives concrete when-to-use guidance by stating that the returned folder IDs feed graph_list_contacts, and the Args section explains the paging strategy ('page by raising skip in steps of top') and that next_link overrides other paging arguments. There is no explicit statement of when not to call it, but the workflow context is clear.

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