Skip to main content
Glama

graph_list_shared_files

Lists files that others have shared with you via Microsoft Graph. Use next_link paging to retrieve additional results; Teams chat attachments require resolving their share link instead.

Instructions

List files other people have shared with the user.

Teams chat attachments do not show up here, so use graph_resolve_share_link on the attachment contentUrl instead. Only $top is passed because sharedWithMe does not support $select or $skip reliably, so page with next_link instead.

Args: top: Maximum number of items to return (default 25). 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_shared_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses important behavioral traits: sharedWithMe does not reliably support $select or $skip, paging must use next_link, and include_next_link controls whether the result is a bare list or {items, next_link}. It does not mention authentication or error conditions, but for a read-only list tool the disclosure is strong.

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?

The description is front-loaded with purpose, then exclusions, then paging constraints, then an Args list. Every sentence earns its place: no repetition, no filler, and the critical caveats (Teams attachments, $select/$skip unreliability) are placed before the parameter details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 3 optional parameters, no annotations, and no output schema, the description covers everything an agent needs: what the tool returns, the exclusion for chat attachments, the paging limitation, and the meaning and interaction of all three parameters. Nothing important is left ambiguous.

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 description coverage is 0%, so the description must fully compensate. It explains each parameter: top is the maximum number of items (default 25), next_link is an opaque URL from a previous call that overrides other paging arguments, and include_next_link controls the result shape (default false returns a bare list). This adds substantial meaning beyond the bare schema types.

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: 'List files other people have shared with the user.' It immediately distinguishes the resource from other file listings and explicitly separates it from Teams chat attachments, naming graph_resolve_share_link as the alternative.

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

Usage Guidelines5/5

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

Explicitly says when not to use this tool (Teams chat attachments) and directs the agent to graph_resolve_share_link on the attachment contentUrl instead. It also explains that paging should use next_link because $select and $skip are unreliable, which guides correct invocation behavior.

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