Skip to main content
Glama

graph_share_file

Create a sharing link for a OneDrive file with configurable view, edit, or embed permissions and anonymous, organization, or user scope.

Instructions

Create a sharing link for a OneDrive file.

Args: file_id: The file ID to share. share_type: Permission type: "view", "edit", or "embed" (default "view"). scope: Share scope: "anonymous", "organization", or "users" (default "organization").

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": {
      "file_id": "<file_id>"
    },
    "name": "graph_share_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoorganization
file_idYes
share_typeNoview

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls short: it never says what permissions are needed, whether an existing link is reused or a new one created, whether links expire or can be revoked, or that the call returns the link URL. It does at least disclose the default share_type and scope, which is the only behavioral context present.

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?

One summary sentence followed by a compact argument list, with the core action front-loaded and no filler. The Args block repeats parameter names from the schema but earns its place by adding the enum values and defaults.

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 three-parameter mutation tool with no annotations and no output schema, the definition covers inputs well but omits the outcome: an agent is not told that the response contains the sharing link/URL, nor what permissions or auth are required to create one. Adequate to invoke, but incomplete for planning around the result.

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 does: it defines all three parameters and, critically, enumerates the accepted values for share_type ('view', 'edit', 'embed') and scope ('anonymous', 'organization', 'users') plus their defaults, none of which appear in the schema. It stops short of explaining what 'users' scope implies (target recipients) or the format of file_id.

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 ('Create a sharing link for a OneDrive file'), which is concrete and actionable. It does not differentiate from plausible siblings such as graph_invite_to_file or graph_list_file_permissions, so an agent must infer that this tool produces a link rather than direct grants.

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, no exclusions, and no mention of alternatives like graph_invite_to_file or graph_resolve_share_link. Only the parameter defaults hint at typical usage, leaving the agent to guess which sharing tool fits a given request.

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