Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Update Group

update_group
Destructive

Update an existing group in Microsoft Graph.

Instructions

Update an existing group in Microsoft Graph.

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": {
      "group_id": "<group_id>",
      "group_data": "<group_data>"
    },
    "name": "update_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYesID of the group to update
group_dataYesDictionary containing group properties to update: - displayName: Display name of the group (optional) - mailNickname: Mail alias for the group (optional) - description: Description of the group (optional) - visibility: "Private" or "Public" for Microsoft 365 groups (optional)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is externally visible. However, the description adds no behavioral context beyond that: it does not explain partial versus full updates, whether omitted fields are preserved, permission requirements, or irreversibility.

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 a single front-loaded sentence with no wasted words. It is concise, though its brevity contributes to under-specification elsewhere rather than over-verbosity here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation tool with a nested update object, the description is too thin. Although an output schema exists, the description should still clarify update semantics and potential side effects that the schema and annotations do not cover.

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 nested group_data schema already documents displayName, mailNickname, description, and visibility. The description adds no parameter meaning beyond the schema, so the baseline 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 states a specific verb and resource: updating an existing group in Microsoft Graph. This clearly distinguishes it from create_group and delete_group by action, though it does not explicitly differentiate it from other update_* tools beyond the resource name.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent must infer usage entirely from the tool name and schema.

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