Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

update-planner-bucket

update-planner-bucket
Destructive

Update a Microsoft Planner bucket's properties—such as name, tasks, or order—by supplying its ID and ETag. Use If-Match to confirm you're changing the latest version, avoiding overwrites.

Instructions

Update the properties of plannerbucket object.

💡 TIP: CRITICAL: Requires If-Match header with ETag from get-planner-bucket (use includeHeaders=true).

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.
If-MatchYesETag value.
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
plannerBucketIdYesValue for the 'plannerBucketId' path segment. Pass it under the name 'plannerBucketId', not as 'id'. Use the 'id' field of the planner bucket object as returned by Microsoft Graph.

Schema Changelog

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

  1. Changed15 schema fields changedv0.145.2
    • removedInput schema / $defs
      Removed value: -{
-  "def0": {
-    "additionalProperties": true,
-    "properties": {
-      "application": {
-        "$ref": "#/$defs/def1"
-      },
-      "device": {
-        "$ref": "#/$defs/def1"
-      },
-      "user": {
-        "$ref": "#/$defs/def1"
-      }
-    },
-    "type": "object"
-  },
-  "def1": {
-    "additionalProperties": true,
-    "properties": {
-      "displayName": {
-        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "id": {
-        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  "def2": {
-    "enum": [
-      "automatic",
-      "noPreview",
-      "checklist",
-      "description",
-      "reference"
-    ],
-    "type": "string"
-  }
-}
    • removedInput schema / properties / body / properties / tasks / items / properties / completedBy / $ref
      Removed value: -"#/$defs/def0"
    • addedInput schema / properties / body / properties / tasks / items / properties / completedBy / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / tasks / items / properties / completedBy / properties
      Added value: +{
+  "application": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "device": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "user": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}
    • addedInput schema / properties / body / properties / tasks / items / properties / completedBy / type
      Added value: +"object"
    • removedInput schema / properties / body / properties / tasks / items / properties / createdBy / $ref
      Removed value: -"#/$defs/def0"
    • addedInput schema / properties / body / properties / tasks / items / properties / createdBy / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / tasks / items / properties / createdBy / properties
      Added value: +{
+  "application": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "device": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "user": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}
    • addedInput schema / properties / body / properties / tasks / items / properties / createdBy / type
      Added value: +"object"
    • removedInput schema / properties / body / properties / tasks / items / properties / details / properties / previewType / $ref
      Removed value: -"#/$defs/def2"
    • addedInput schema / properties / body / properties / tasks / items / properties / details / properties / previewType / enum
      Added value: +[
+  "automatic",
+  "noPreview",
+  "checklist",
+  "description",
+  "reference"
+]
    • addedInput schema / properties / body / properties / tasks / items / properties / details / properties / previewType / type
      Added value: +"string"
    • removedInput schema / properties / body / properties / tasks / items / properties / previewType / $ref
      Removed value: -"#/$defs/def2"
    • addedInput schema / properties / body / properties / tasks / items / properties / previewType / enum
      Added value: +[
+  "automatic",
+  "noPreview",
+  "checklist",
+  "description",
+  "reference"
+]
    • addedInput schema / properties / body / properties / tasks / items / properties / previewType / type
      Added value: +"string"
  2. Changed11 schema fields changedv0.134.4
    • addedInput schema / $defs
      Added value: +{
+  "def0": {
+    "additionalProperties": true,
+    "properties": {
+      "application": {
+        "$ref": "#/$defs/def1"
+      },
+      "device": {
+        "$ref": "#/$defs/def1"
+      },
+      "user": {
+        "$ref": "#/$defs/def1"
+      }
+    },
+    "type": "object"
+  },
+  "def1": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "def2": {
+    "enum": [
+      "automatic",
+      "noPreview",
+      "checklist",
+      "description",
+      "reference"
+    ],
+    "type": "string"
+  }
+}
    • addedInput schema / properties / body / properties / tasks / items / properties / completedBy / $ref
      Added value: +"#/$defs/def0"
    • removedInput schema / properties / body / properties / tasks / items / properties / completedBy / additionalProperties
      Removed value: -true
    • removedInput schema / properties / body / properties / tasks / items / properties / completedBy / properties
      Removed value: -{
-  "application": {
-    "additionalProperties": true,
-    "properties": {
-      "displayName": {
-        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "id": {
-        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  "device": {
-    "$ref": "#/properties/body/properties/tasks/items/properties/completedBy/properties/application"
-  },
-  "user": {
-    "$ref": "#/properties/body/properties/tasks/items/properties/completedBy/properties/application"
-  }
-}
    • removedInput schema / properties / body / properties / tasks / items / properties / completedBy / type
      Removed value: -"object"
    • changedInput schema / properties / body / properties / tasks / items / properties / createdBy / $ref
      Previous value: -"#/properties/body/properties/tasks/items/properties/completedBy"New value: +"#/$defs/def0"
    • addedInput schema / properties / body / properties / tasks / items / properties / details / properties / previewType / $ref
      Added value: +"#/$defs/def2"
    • removedInput schema / properties / body / properties / tasks / items / properties / details / properties / previewType / enum
      Removed value: -[
-  "automatic",
-  "noPreview",
-  "checklist",
-  "description",
-  "reference"
-]
    • removedInput schema / properties / body / properties / tasks / items / properties / details / properties / previewType / type
      Removed value: -"string"
    • changedInput schema / properties / body / properties / tasks / items / properties / previewType / $ref
      Previous value: -"#/properties/body/properties/tasks/items/properties/details/properties/previewType"New value: +"#/$defs/def2"
    • changedInput schema / properties / plannerBucketId / description
      Previous value: -"Path parameter: plannerBucketId"New value: +"Value for the 'plannerBucketId' path segment. Pass it under the name 'plannerBucketId', not as 'id'. Use the 'id' field of the planner bucket object as returned by Microsoft Graph."
  3. Changed1 schema field changedv0.131.2
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
  4. 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"
+}
  5. Addedv0.114.0
  6. Removedv0.112.2
  7. Addedv0.110.0
  8. Removedv0.108.0
  9. Addedv0.96.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation nature is disclosed. The description adds the critical If-Match header requirement with a pointer to get-planner-bucket and includeHeaders=true, which is behavioral context beyond the annotations. However, it does not mention partial vs full update semantics, error behavior if the ETag is stale, or the confirm gate (though that is covered in the schema). It does not contradict the annotations.

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?

The description is two sentences: a clear purpose statement followed by a compact, high-value tip. It is front-loaded with the action and then provides a critical operational note. The phrasing is slightly awkward ('plannerbucket' without a space) but overall concise and efficient. It avoids unnecessary fluff.

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?

Given the tool's complexity (6 parameters, nested body object, destructive mutation), the description is minimal. It covers the essential If-Match requirement but omits update semantics (e.g., only provided fields are updated), what happens with conflicting ETags, and any prerequisites like existing bucket existence. However, the rich schema descriptions for parameters and the body partially compensate. An agent would need to rely heavily on the schema and external knowledge to call it correctly.

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

Parameters3/5

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

Schema description coverage is 83%, meaning most parameters (If-Match, includeHeaders, excludeResponse, plannerBucketId) have descriptions in the schema. The body object is deeply nested with its own field descriptions. The tool description adds no new meaning for parameters; the If-Match tip merely repeats what the schema already says ('ETag value'). With high schema coverage, the baseline of 3 applies.

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 clearly states the action: 'Update the properties of plannerbucket object.' This is a specific verb-resource pairing that distinguishes it from create/delete siblings by virtue of the word 'update'. However, it does not explicitly contrast with these alternatives, so it lacks strong differentiation.

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?

The description provides no guidance on when to use this tool versus create-planner-bucket, delete-planner-bucket, or get-planner-bucket. It only includes a required-header tip, which is a how-to detail, not a usage context. There are no alternatives named, no conditions for selection, and no exclusions. This leaves the agent to infer usage from the tool name alone.

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