Skip to main content
Glama

graph_get_channel_files_folder

Retrieves the SharePoint folder that stores a Teams channel's files and returns the folder ID and drive ID needed by OneDrive file tools.

Instructions

Get the SharePoint folder that stores a channel's files.

This is the bridge from a channel to its SharePoint folder. Pass the returned folder ID together with its 'parentReference.driveId' as drive_id to the OneDrive file tools, which need both to reach a drive other than your own. Needs the Files.Read.All permission.

Args: team_id: The team ID (from graph_list_teams). channel_id: The channel ID (from graph_list_channels). include_children: Whether to also list the folder contents (default false). When true the result is {"folder": ..., "children": [...]}. top: Maximum number of children to return (default 50, maximum 50).

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": {
      "team_id": "<team_id>",
      "channel_id": "<channel_id>"
    },
    "name": "graph_get_channel_files_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
team_idYes
channel_idYes
include_childrenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose the required Files.Read.All permission, the conditional return shape when include_children is true, and the children count defaults. It stops short of covering failure modes (e.g., a channel with no SharePoint folder) or pagination behavior.

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?

Front-loaded one-sentence purpose, then the bridging behavior and permission, then a compact Args block. Nothing is padding, and the Args block is necessary given the undocumented schema.

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 4-parameter read tool with no annotations and no output schema, the description covers purpose, permission, return shape, and downstream chaining. It leaves out the structure of the returned folder object and what happens past the 50-child cap, which an agent would still need to discover by calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description compensates fully: it documents where team_id and channel_id come from, the default and effect of include_children including the resulting object shape, and the default and cap for top. It also clarifies that top bounds children only, which is meaningful for a read call.

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?

States a specific verb and resource ("Get the SharePoint folder that stores a channel's files") and immediately frames the tool's role as a bridge from channel to drive. The mention that the returned folder ID plus 'parentReference.driveId' are what the OneDrive file tools need makes it distinguishable from the file-listing siblings.

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 clear when-to-use context by naming the downstream step (pass folder ID and driveId as drive_id to OneDrive file tools for another drive) and the upstream sources of the IDs (graph_list_teams, graph_list_channels). It does not state any exclusion or when-not-to-use case, so this falls just short of the top band.

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