Skip to main content
Glama

List OneDrive Files

list_drive_items
Read-only

Lists files and folders in OneDrive by root, folder ID, or path, with optional pagination to retrieve all results.

Instructions

List files and folders in OneDrive

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

Input Schema

NameRequiredDescriptionDefault
folder_idNoFolder ID (omit for root)
folder_pathNoFolder path (e.g., 'Documents' or 'Documents/Subfolder')
fetch_all_pagesNoFetch all pages of results (max 50 pages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds nothing beyond that: it does not say whether listing is shallow or recursive, how results are ordered, or that paging is bounded (the schema's fetch_all_pages hints at a 50-page cap that is never surfaced as behavior). For a listing tool that can silently truncate, this is a meaningful gap.

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 single front-loaded sentence with no filler; it is efficiently structured, though its brevity is achieved by omitting information rather than by tight editing.

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 simple three-parameter read-only listing tool with full schema coverage and no output schema, the description is just barely sufficient. It would need at minimum the shallow/recursive behavior and a note on pagination or truncation to be complete.

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 three parameters (folder_id, folder_path, fetch_all_pages) are documented in the input schema and the baseline is 3. The description contributes no additional meaning about how folder_id and folder_path interact or which takes precedence.

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?

"List files and folders in OneDrive" states a specific verb (list) and resource (OneDrive files/folders), and the OneDrive qualifier implicitly separates it from the SharePoint-oriented sibling list_site_items. It does not, however, explicitly contrast itself with siblings such as get_drive_item or search_files.

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 guidance at all: nothing says whether this is for browsing a known folder versus finding content by name (search_files), nor when to prefer get_drive_item for a single item. The agent must infer the routing decision entirely from tool names.

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