Skip to main content
Glama
PagerDuty

pagerduty-mcp

Official
by PagerDuty

list_users

Read-onlyIdempotent

List PagerDuty users filtered by name or team IDs to quickly find specific team members.

Instructions

List users, optionally filtering by name (query) and team IDs.

Args:
    query: Filters the result, showing only the records whose name matches the query.
    teams_ids: Filter users by team IDs.
    limit: Pagination limit. Default 100.

Returns:
    List of users matching the criteria.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryNo
teams_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
responseYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds pagination default and return type, but no additional behavioral traits beyond what annotations already provide.

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?

Concise, front-loaded with purpose, then args, then returns. Every sentence is necessary and well-structured.

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

Completeness5/5

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

Given the simple nature of the tool (list with filters), annotations covering safety, and an output schema present, the description is complete with no missing aspects.

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

Parameters5/5

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

Schema description coverage is 0%, so description fully compensates by explaining each parameter (query filters by name, teams_ids filters by team, limit for pagination) with clear semantics.

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?

Clearly states verb 'List' and resource 'users', with optional filtering options. However, it does not explicitly differentiate from sibling list tools like list_team_members, which might also list users filtered by team.

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?

Implies usage (list users with optional filters) but lacks explicit when-to-use or when-not-to-use guidance, nor mentions alternatives among sibling tools.

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/PagerDuty/pagerduty-mcp-server'

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