Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria

upload-my-profile-photo

upload-my-profile-photo
Destructive

Upload a new profile photo for the signed-in Microsoft 365 user. Accepts base64-encoded JPEG up to 4 MB; Microsoft 365 automatically generates HD-sized versions.

Instructions

Update the photo for the specified contact, group, team, or user in a tenant. The size of the photo you can update to is limited to 4 MB. You can use either PATCH or PUT for this operation.

đź’ˇ TIP: Uploads a new profile photo for the signed-in user. Body is a base64-encoded string of the image bytes (the server decodes before PUT). Photo must be JPEG, max 4 MB; the base64 travels as a tool argument and a truncated one is written without error, so resize before encoding instead of emitting a large string. Microsoft 365 generates HD downsized variants automatically (48x48, 64x64, 96x96, 120x120, 240x240, 360x360, 432x432, 504x504, 648x648). For work or school accounts, ProfilePhoto.ReadWrite.All is the more granular alternative permission. Use download-bytes with target=/me/photo/$value to retrieve the current photo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesBase64-encoded file content. The server decodes it and PUTs the raw bytes to Microsoft Graph.
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.
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. Changed1 schema field changedv0.131.2
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
  2. 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"
      +}
  3. Addedv0.114.0
  4. Removedv0.112.2
  5. Addedv0.110.0
  6. Removedv0.108.0
  7. Addedv0.105.0

TDQS

A4.2/5.0
Behavior5/5

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

Even though annotations already mark this as destructive/non-read-only, the description adds genuine behavioral value: the 4 MB size ceiling, the fact that a truncated base64 payload is written 'without error' so the caller must validate, the JPEG-only constraint, server-side decoding behavior, and the auto-generated thumbnails with exact pixel sizes. This makes failure modes and side effects far more predictable.

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?

At ~146 words the text is longer than average, but it is efficiently structured with a lead paragraph, a tip, and a retrieval hint, and almost every clause earns its place. The 4 MB limit is mentioned twice and the guidance could be slightly tightened, but it remains scannable and front-loaded.

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 destructive write tool with no output schema, the description covers all the key operational aspects: expected format, size caps, error behavior, permissions, and the companion read operation. The only substantive gap is the unresolved scope confusion (tenant-wide entity vs. signed-in user), plus little clarity on the response shape beyond the confirm-gate error.

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 coverage is 100% with already-rich per-parameter documentation (e.g., `confirm` explains the gate and error contract). The description supplements this by explaining what the base64 payload becomes on the server (decoded to raw bytes, PUT via Graph), warns about large-string risk, and reinforces JPEG/4MB validation rules—adding context around the schema rather than repeating it.

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?

The description opens with a clear verb-resource-scope pattern ('Update the photo for the specified contact, group, team, or user') that immediately distinguishes it from sibling tools. However, this scope statement conflicts with the tip, which says it uploads 'for the signed-in user'—and the schema exposes no entity-ID parameter—so an agent might be misled about targeting arbitrary entities. Minor internal redundancy with '4 MB' stated twice.

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?

Excellent guidance: it explicitly names the sibling `download-bytes` with a full example target for the inverse operation, and it flags the ProfilePhoto.ReadWrite.All permission as a more granular alternative for work/school accounts. It does not, however, address when to choose this over other update/upload siblings (e.g., upload-file-content), leaving some comparison gaps.

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