Skip to main content
Glama

graph_list_site_drives

List the document libraries of a SharePoint site by site ID, with paging, to locate and access files stored in that site.

Instructions

List the document libraries of a SharePoint site.

Args: site_id: The SharePoint site ID (from graph_search_sites). 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_id": "<site_id>"
    },
    "name": "graph_list_site_drives"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
site_idYes
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?

No annotations are supplied, so the description carries the full burden, and it does real work: it discloses the 50-item server cap, the skip-stepping paging strategy, that next_link overrides other paging arguments, and that include_next_link changes the response shape between a bare list and {items, next_link}. It does not mention permission requirements or error behavior, which keeps it below a 5.

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?

The one-line purpose sentence is front-loaded and the remaining content is a compact per-parameter breakdown with no filler. The docstring-style 'Args:' block is slightly verbose but every line carries information.

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 output schema and no annotations, the definition covers paging mechanics and return-shape switching well enough to invoke correctly. It omits what a drive object contains and any permission prerequisites, which are the remaining gaps.

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 compensate, and it documents all four parameters with defaults, meaning, and interaction rules. The only flaw is the reference to paging 'in steps of top' when no top parameter exists in the schema, which could confuse an agent about whether a page-size argument is accepted.

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?

States a specific verb and resource: 'List the document libraries of a SharePoint site.' An agent can tell this apart from generic drive or file listing tools because the resource is scoped to a site and the required site_id makes that explicit. It stops short of naming a sibling such as graph_list_drives to draw the distinction outright.

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?

Gives a clear prerequisite and workflow hint by noting site_id comes 'from graph_search_sites', and explains paging behavior including when to use next_link versus skip. It does not state when-not to use this tool or name an alternative for cross-site or user-level drive listing.

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