Skip to main content
Glama
Sign In
AliMail Admin MCP

AliMail Admin MCP

by mfc-open
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

批量获取用户信息

get_users_by_ids
Read-onlyIdempotent

Retrieves user information in batch from a list of user IDs, returning only existing users and supporting extra fields through a select parameter.

Instructions

根据用户 ID 列表批量获取用户信息（最多 100 个），不存在的 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": {
      "ids": "<ids>"
    },
    "name": "get_users_by_ids"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
selectNo透传 $select，指定额外返回字段，多个用英文逗号分隔，如 phone,managerEmail,isHidden

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds a genuine behavioral fact beyond structured data: IDs that do not exist are silently omitted from the result rather than erroring, which an agent needs to know to interpret a shorter-than-requested response. It does not cover result ordering or pagination, so it is not a 5.

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?

A single compact sentence with the operation stated first and the two caveats (100 cap, missing IDs dropped) trailing it — no filler. Slightly redundant with the schema's maxItems constraint, which keeps it from being a 5.

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?

For a simple two-parameter read tool with rich annotations and no output schema, the description covers the essentials of scope and edge-case behavior. It still leaves open what fields are returned by default and whether 'select' is required to obtain non-default fields, which matters given the partially documented schema.

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 coverage is 50%: the 'select' parameter is documented in the schema, but 'ids' carries no schema description. The description only restates the 100-item maximum already encoded as maxItems and does not clarify the expected ID format (userid vs. email) or whether result order follows input order, so it does not fully compensate for the gap.

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 names a specific verb and resource — batch fetching user information by an ID list — which is clearly distinct from single-user or department-listing siblings. It does not explicitly name a sibling such as get_user or list_users to contrast against, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word '批量' (batch) and the 100-ID cap imply this is the tool for resolving many known IDs at once, which implicitly steers an agent away from single-record calls. However, there is no explicit statement of when to prefer this over get_user or list_users, and no prerequisites or exclusions are given.

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