Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

create-upload-session

create-upload-session
Destructive

Creates an upload session for large file transfers, returning a pre-authenticated upload URL for direct PUT requests to Microsoft 365.

Instructions

Create an upload session.

💡 TIP: For large file uploads (no size limit, and no minimum unlike the Outlook attachment session). Returns a pre-authenticated uploadUrl; the caller PUTs the bytes there itself. This server does not perform the PUT. For new files use path: /items/{parentId}:/{fileName}:/createUploadSession. Body (optional): { item: { '@microsoft.graph.conflictBehavior': 'rename' } }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
confirmNoFor destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: "confirmation_required" } without touching user data.
driveIdYesValue for the 'driveId' path segment. Pass it under the name 'driveId', not as 'id'. Use the 'id' field of the drive object as returned by Microsoft Graph.
driveItemIdYesValue for the 'driveItemId' path segment. Pass it under the name 'driveItemId', not as 'id'. Use the 'id' field of the drive item object as returned by Microsoft Graph.
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.134.4
  2. Removedv0.131.2
  3. Changed1 schema field changedv0.131.1
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "For destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: \"confirmation_required\" } without touching user data.",
+  "type": "boolean"
+}
  4. Changed4 schema fields changedv0.125.0
    • removedInput schema / properties / body / properties / item / additionalProperties
      Removed value: -true
    • addedInput schema / properties / body / properties / item / anyOf
      Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "description": {
+        "description": "Provides a user-visible description of the item. Read-write. Only on OneDrive Personal.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "driveItemSource": {
+        "additionalProperties": true,
+        "properties": {
+          "application": {
+            "enum": [
+              "teams",
+              "yammer",
+              "sharePoint",
+              "oneDrive",
+              "stream",
+              "powerPoint",
+              "office",
+              "loki",
+              "loop",
+              "other",
+              "unknownFutureValue"
+            ],
+            "type": "string"
+          },
+          "externalId": {
+            "description": "The external identifier for the drive item from the source.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "fileSize": {
+        "description": "Provides an expected file size to perform a quota check before uploading. Only on OneDrive Personal.",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "fileSystemInfo": {
+        "additionalProperties": true,
+        "properties": {
+          "createdDateTime": {
+            "anyOf": [
+              {
+                "description": "The UTC date and time the file was created on a client.",
+                "format": "date-time",
+                "pattern": "^[0-9]{4,}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,12})?(Z|[+-][0-9][0-9]:[0-9][0-9])$",
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The UTC date and time the file was created on a client."
+          },
+          "lastAccessedDateTime": {
+            "anyOf": [
+              {
+                "description": "The UTC date and time the file was last accessed. Available for the recent file list only.",
+                "format": "date-time",
+                "pattern": "^[0-9]{4,}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,12})?(Z|[+-][0-9][0-9]:[0-9][0-9])$",
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The UTC date and time the file was last accessed. Available for the recent file list only."
+          },
+          "lastModifiedDateTime": {
+            "anyOf": [
+              {
+                "description": "The UTC date and time the file was last modified on a client.",
+                "format": "date-time",
+                "pattern": "^[0-9]{4,}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,12})?(Z|[+-][0-9][0-9]:[0-9][0-9])$",
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The UTC date and time the file was last modified on a client."
+          }
+        },
+        "type": "object"
+      },
+      "mediaSource": {
+        "additionalProperties": true,
+        "properties": {
+          "contentCategory": {
+            "enum": [
+              "meeting",
+              "liveStream",
+              "presentation",
+              "screenRecording",
+              "story",
+              "profile",
+              "chat",
+              "note",
+              "comment",
+              "unknownFutureValue"
+            ],
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "name": {
+        "description": "The name of the item (filename and extension). Read-write.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  }
+]
    • removedInput schema / properties / body / properties / item / properties
      Removed value: -{}
    • removedInput schema / properties / body / properties / item / type
      Removed value: -"object"
  5. Addedv0.114.0
  6. Removedv0.112.2
  7. Addedv0.110.0
  8. Removedv0.108.0
  9. Addedv0.96.0

TDQS

A4/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=true), the description discloses that the server does not perform the PUT—the caller must upload bytes to the returned URL. It also notes the body is optional (though this contradicts the schema) and provides a conflictBehavior example, adding meaningful context.

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 compact and well-structured. It front-loads the purpose, uses a tip to highlight the key use case, and includes only essential details about behavior and body example. No redundant or filler content.

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?

The description covers the core purpose, use case, and the critical PUT behavior. However, the erroneous 'optional' body representation introduces a reliability gap, and it does not address generic parameters like confirm, includeHeaders, or excludeResponse. These omissions, combined with the contradiction, leave it incomplete for a tool with this many parameters and complex body schema.

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

Parameters2/5

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

Schema coverage is high (83%), so the baseline is 3, but the description directly contradicts the schema by stating 'Body (optional)' while the input schema lists body as required. This misleading statement could cause the agent to omit a required parameter. The conflictBehavior example is useful, but the false optionality is a severe flaw.

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 'Create an upload session' and explains it returns a pre-authenticated uploadUrl for large file uploads. It distinguishes itself from the Outlook attachment upload session by noting no size limit and no minimum, making the tool's purpose unambiguous.

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?

The description explicitly recommends this tool for large file uploads and contrasts it with the Outlook attachment session. It also gives an example path for new files. However, it does not mention when to prefer it over other upload tools like upload-file-content, so the alternatives are only partially covered.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Softeria/ms-365-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server