Skip to main content
Glama
EntraID MCP Server

EntraID MCP Server

by baoduy

Get Group Members

get_group_members
Read-only

Get members of a group by group ID (up to the specified limit, with paging).

Instructions

Get members of a group by group ID (up to the specified limit, with paging).

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>"
    },
    "name": "get_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
group_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuine context the annotations don't: results are capped by a limit and support paging. It omits any permission/consent scope requirement and any indication of what a member record contains (though an output schema exists, so return shape is covered elsewhere).

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?

One sentence, front-loaded with the resource and the deciding key, and the parenthetical adds scoping facts rather than filler. Nothing to cut.

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?

Annotations cover the read-only profile and an output schema covers the return shape, so the description need not explain results. It is still incomplete in a way that matters: it says 'with paging' but the schema exposes no offset/token parameter, leaving the agent unclear on how to page at all, and it says nothing about the default or ceiling of limit.

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 0%, so the description must carry the parameter burden. It does partially: group_id is the target group and limit is a page size with paging. But it never states the default (100), the maximum allowed limit, or the expected group_id format (GUID vs. name), which is the main failure mode for this call.

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?

Specific verb + resource + filter: 'Get members of a group by group ID'. Clearly distinguishes the direction of the relationship from siblings like get_user_groups (user→groups), add_group_member, and remove_group_member. It stops short of naming a sibling to route away from, so it is not a 5.

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 explicit when-to-use statement and no named alternative. An agent must infer from the name that this is the way to enumerate a group's membership versus add_group_member/remove_group_member or search_users. Usage is only implicit.

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