PagerDuty MCP Server

get_users

Retrieve PagerDuty users by name, team, or user ID to look up people and inspect specific user details.

Instructions

Get PagerDuty users by filters or get details for a specific user ID.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_users"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Limit the number of results (optional). Not used if `user_id` is provided.
`query`	No	Filter users whose names contain the search query (optional). Not used if `user_id` is provided.
`include`	No	List of fields to include in the response. If specified, only these fields will be returned for each user
`user_id`	No	The user ID to retrieve (optional, cannot be used with any other filters).
`team_ids`	No	Filter results to only users assigned to teams with the given IDs (optional, cannot be used with current_user_context). Not used if `user_id` is provided.
`current_user_context`	No	Use current user's team IDs to filter (default: True); errors if the current user belongs to no teams. Not used if `user_id` is provided.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv4.0.7Oct 27, 2026

changedInput schema / properties / current_user_context / description

Previous value: -"Use current user's team IDs to filter (default: True). Not used if `user_id` is provided."New value: +"Use current user's team IDs to filter (default: True); errors if the current user belongs to no teams. Not used if `user_id` is provided."

Changed1 schema field changedv4.0.1May 12, 2026

addedInput schema / properties / include

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "List of fields to include in the response. If specified, only these fields will be returned for each user"
+}

Changed12 schema fields changedv3.1.4May 8, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / current_user_context / description

Added value: +"Use current user's team IDs to filter (default: True). Not used if `user_id` is provided."

removedInput schema / properties / current_user_context / title
```
Removed value: -"Current User Context"
```

addedInput schema / properties / limit / description

Added value: +"Limit the number of results (optional). Not used if `user_id` is provided."

removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```

addedInput schema / properties / query / description

Added value: +"Filter users whose names contain the search query (optional). Not used if `user_id` is provided."

removedInput schema / properties / query / title
```
Removed value: -"Query"
```

addedInput schema / properties / team_ids / description

Added value: +"Filter results to only users assigned to teams with the given IDs (optional, cannot be used with current_user_context). Not used if `user_id` is provided."

removedInput schema / properties / team_ids / title
```
Removed value: -"Team Ids"
```

addedInput schema / properties / user_id / description

Added value: +"The user ID to retrieve (optional, cannot be used with any other filters)."

removedInput schema / properties / user_id / title
```
Removed value: -"User Id"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedv1.0.0Aug 18, 2025

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden and discloses nothing behavioral: no mention of pagination, auth/permission requirements, or the significant default that current_user_context=true silently narrows results to the caller's teams and errors if the user has none. That side effect is only visible by reading the schema.

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 front-loaded sentence that wastes no words and puts the primary verb first. It is arguably too terse given the two-mode behavior, but nothing in it is filler.

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?

An output schema exists and all six parameters are documented in the schema, so basic completeness is met. Still missing is any explanation of how the two modes interact and the team-scoped default behavior, which matters for a tool with six optional parameters and no annotations.

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%, so every parameter including limit, query, include, team_ids and the current_user_context default is already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 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?

States a specific verb and resource ('Get PagerDuty users') and distinguishes its two operating modes: filtered list vs single-ID lookup. It does not, however, differentiate itself from sibling tools like list_users_oncall or build_user_context, which an agent must choose between.

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 dual-mode framing implies when each path applies (filter list vs user_id), but there is no explicit guidance on when to prefer this over list_users_oncall or build_user_context, nor on prerequisites such as needing team context.

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

Deploy Server