Skip to main content
Glama

list_iam_users

Retrieve all IAM users from your AWS account to manage access permissions and audit user accounts.

Instructions

Lists IAM users in the AWS account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_iam_users' tool. It sends a ListUsersCommand to the IAM client, maps the response to extract UserName, UserId, Arn, and CreateDate, and returns the JSON stringified list.
    if (name === "list_iam_users") {
        const command = new ListUsersCommand({});
        const response = await iamClient.send(command);
        const users = response.Users?.map(u => ({
            UserName: u.UserName,
            UserId: u.UserId,
            Arn: u.Arn,
            CreateDate: u.CreateDate
        })) || [];
    
        return {
            content: [
                {
                    type: "text",
                    text: JSON.stringify(users, null, 2)
                }
            ]
        }
    }
  • src/index.ts:132-138 (registration)
    Registration of the 'list_iam_users' tool in the ListToolsRequestHandler, including its name, description, and empty input schema (no parameters required).
        name: "list_iam_users",
        description: "Lists IAM users in the AWS account.",
        inputSchema: {
            type: "object",
            properties: {}
        }
    },
  • Input schema for 'list_iam_users' tool: an empty object, indicating no input parameters are needed.
    inputSchema: {
        type: "object",
        properties: {}
    }
  • Initialization of the IAMClient used by the list_iam_users handler.
    const iamClient = new IAMClient({});
  • Import of IAMClient and ListUsersCommand required for the list_iam_users tool implementation.
    import { IAMClient, ListUsersCommand, ListAccessKeysCommand, ListMFADevicesCommand } from "@aws-sdk/client-iam";
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'lists' users, implying a read-only operation, but doesn't disclose behavioral traits like pagination, rate limits, authentication requirements, or output format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly, which is ideal for a simple tool.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. However, it lacks context on output (e.g., what data is returned) and behavioral details, which could be helpful for an agent. It meets basic needs but has clear gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, earning a baseline score of 4 since it doesn't need to compensate for any schema gaps.

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 clearly states the verb ('Lists') and resource ('IAM users in the AWS account'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'list_users_without_mfa' or other user-related tools, which would require more specificity for a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., AWS permissions), context (e.g., for auditing or troubleshooting), or how it differs from other list tools in the sibling set, leaving the agent with no usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bhaveshopss/MCP-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server