sharepoint-mcp

List_SharePoint_Documents

List all documents and metadata from a SharePoint folder, using 'root' or empty string for the document library root, and paths like 'Reports/2024' for nested folders.

Instructions

List all documents (with metadata) inside a SharePoint folder. For Graph API, use empty string or 'root' for the document library root. For nested folders, use paths like 'Reports' or 'Reports/2024'.

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

Input Schema

Name	Required	Description	Default
`folder_name`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 28, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are present, so the description bears full responsibility. It discloses path syntax but omits critical behaviors like recursion, pagination, error handling, or permission requirements. The agent cannot infer how deep the listing goes or what happens with empty folders.

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?

Two sentences, no fluff. The first sentence states the primary purpose; the second provides actionable usage details. Every word earns its place.

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?

With a single optional parameter and an output schema present, the description covers the basic usage. However, it lacks details on recursion, permissions, and how the tool behaves with large result sets. Sibling differentiation is implied but not explicit.

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 0% (no parameter descriptions), but the description compensates by explaining valid values for folder_name: empty string/'root' for root, and path patterns like 'Reports/2024' for nested folders. This adds essential semantic meaning beyond the schema.

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 the verb ('List') and resource ('all documents with metadata inside a SharePoint folder'), and it distinguishes from sibling tools like List_SharePoint_Folders by focusing on documents. The path usage tips further clarify 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 the use case (listing documents in a folder) but does not explicitly guide when to use this tool over alternatives such as Search_SharePoint or Get_File_Metadata. No exclusions or when-not-to-use advice is provided.

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

Deploy Server