Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get-subscription

get-subscription
Read-only

Retrieve a Microsoft 365 webhook subscription by ID, returning resource, change type, notification URL, and expiration. Get full subscription details for change notifications.

Instructions

Retrieve the properties and relationships of a subscription. See the table in the Permissions section for the list of resources that support subscribing to change notifications.

đź’ˇ TIP: Gets a specific webhook subscription by id. Use list-subscriptions to find the id. Returns full subscription details including resource, changeType, notificationUrl, expirationDateTime, applicationId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectNoComma-separated fields to return, e.g. id,subject,from,receivedDateTime
fetchAllPagesNoFollow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a small $top first, then paginate or narrow with $filter/$search.
includeHeadersNoInclude response headers (including ETag) in the response metadata
subscriptionIdYesValue 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.
excludeResponseNoExclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.154.2
    • addedInput schema / properties / select / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • removedInput schema / properties / select / type
      Removed value: -"string"
  2. Changed1 schema field changedv0.134.4
    • changedInput schema / properties / subscriptionId / description
      Previous value: -"Path parameter: subscriptionId"New value: +"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."
  3. Changed1 schema field changedv0.131.2
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
  4. Addedv0.114.0
  5. Removedv0.112.2
  6. Addedv0.110.0
  7. Removedv0.108.0
  8. Addedv0.96.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful context about return contents ('full subscription details including resource, changeType, notificationUrl, expirationDateTime, applicationId') but does not disclose additional behavioral traits such as auth requirements, rate limits, or error conditions.

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 compact and front-loaded with the core purpose, followed by a practical tip. The permission reference adds context but is somewhat generic; overall no sentence is wasted, though the two purpose statements are slightly redundant.

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 single-required-parameter read operation with no output schema, the description covers how to identify the target, what will be returned, and where to find permission-relevant resources. It lacks detail on error cases or response shape beyond the listed fields, but it is complete enough for correct invocation.

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 100%, and the parameter descriptions are already detailed, especially for subscriptionId, select, and fetchAllPages. The description does not add parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 uses a specific verb and resource ('Retrieve the properties and relationships of a subscription') and immediately distinguishes itself from listing by stating 'Gets a specific webhook subscription by id.' This clearly separates it from sibling list-subscriptions without requiring schema inspection.

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 routes the agent to list-subscriptions to find the id, which is a clear alternative and usage signal. It implies this tool is for retrieval when an id is already known, though it does not explicitly state when not to use it or mention the write-oriented sibling tools.

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