ms-365-mcp-server

delete-subscription

delete-subscription

Destructive

Delete a webhook subscription to stop change notifications and clean up stale subscriptions. Use this to halt notifications when no longer needed.

Instructions

Delete a subscription. For the list of resources that support subscribing to change notifications, see the table in the Permissions section.

💡 TIP: Deletes a webhook subscription. No further change notifications will be sent. Use this to clean up stale subscriptions or stop receiving notifications. Use list-subscriptions to find the id.

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": {
      "subscriptionId": "<subscriptionId>"
    },
    "name": "delete-subscription"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	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.
`If-Match`	No	ETag
`includeHeaders`	No	Include response headers (including ETag) in the response metadata
`subscriptionId`	Yes	Value for the 'subscriptionId' path segment. Pass it under the name 'subscriptionId', not as 'id'. Use the 'id' field of the subscription object as returned by Microsoft Graph.
`excludeResponse`	No	Exclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0-developmentAug 24, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, covering the safety profile. The description adds meaningful behavioral context by stating that no further change notifications will be sent after deletion, which is a direct consequence beyond the annotations. No contradiction.

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 two short sentences plus a tip. No fluff, all content earns its place, and the core action is front-loaded. The tip is supplementary but highly relevant and concise.

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 delete operation with no output schema, the description covers the core function, the consequence, and how to locate the target. It omits details like idempotency or error handling, but those are not essential for an agent to invoke correctly. The permissions link offers additional context. Complete enough for the complexity.

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%, so all parameters are already documented. The description's tip ('Use list-subscriptions to find the id') adds practical guidance for the subscriptionId parameter that goes beyond the schema's purely positional description. This extra hint elevates it above the baseline 3.

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 states a specific verb and resource ('Delete a subscription') and immediately clarifies it refers to webhook subscriptions via the tip. It is clearly distinguishable from siblings like update-subscription, get-subscription, and list-subscriptions. The purpose is unambiguous.

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 states when to use the tool ('clean up stale subscriptions or stop receiving notifications') and provides a concrete pointer to the sibling tool list-subscriptions for finding the target id. It gives actionable context without needing inference.

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

Deploy Server