Skip to main content
Glama
Microsoft 365 MCP Server

Microsoft 365 MCP Server

by Softeria

remove-account

Removes a Microsoft account from the cache using its email address or account ID, clearing stale or unwanted cached accounts. Use list-accounts to discover available accounts.

Instructions

Remove a Microsoft account from the cache. Accepts email address (e.g. user@outlook.com) or account ID. Use list-accounts to discover available accounts.

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": {
      "account": "<account>"
    },
    "name": "remove-account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYesEmail address or account ID of the account to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.134.4
  2. Removedv0.131.2
  3. Addedv0.114.0
  4. Removedv0.112.2
  5. Addedv0.110.0
  6. Removedv0.108.0
  7. Changed3 schema fields changedv0.96.0
    • addedInput schema / properties / account
      Added value: +{
      +  "description": "Email address or account ID of the account to remove",
      +  "type": "string"
      +}
    • removedInput schema / properties / accountId
      Removed value: -{
      -  "description": "The account ID to remove",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "accountId"
      -]New value: +[
      +  "account"
      +]
  8. First observedv0.31.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations declare readOnlyHint=false but not destructiveHint, so the description's clarification that removal is only 'from the cache' is materially useful — it signals the underlying Microsoft account is not deleted. It still stays silent on reversibility (can the account be re-added?) and on behavior when the target does not exist.

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?

Three short sentences, each front-loaded with a distinct piece of information: what is removed, what input is accepted, and how to find valid targets. Nothing is redundant or padded.

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 one-parameter, no-output-schema tool this covers what an agent needs to call it correctly, including the cache-only scope. The only meaningful omission is the result of removing a non-existent or already-removed account.

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 single required parameter is already documented as 'Email address or account ID'. The description's example (user@outlook.com) and format note largely restate the schema, so this is baseline rather than added value.

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?

States a specific verb and resource ('Remove a Microsoft account') and narrows the scope to 'from the cache', which is what makes this tool distinct from delete-onedrive-file or other destructive siblings. An agent can tell immediately what the tool acts on.

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?

Points to list-accounts as the way to discover valid targets, which is the main prerequisite an agent needs. It does not address when to prefer this over adjacent session tools like logout or select-account, but the intended usage context is clear.

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