Skip to main content

​
Overview

Updates the configuration of an existing service in your PagerDuty account. You can modify the service name, description, escalation policy, and team associations.
This is a write tool that modifies your PagerDuty account. You must enable write mode with the --enable-write-tools flag to use this tool.

​
Parameters

​
service_id
string
required
The ID of the service to update.Example: PSERVICE1
​
service_data
ServiceCreate
required
The updated service data.

​
Response

Returns the updated Service object with all current field values.
​
id
string
The unique identifier for the service.
​
type
string
The type of the object (always "service").
​
name
string
The updated name of the service.
​
description
string
The updated description of the service.
​
escalation_policy
EscalationPolicyReference
Reference to the escalation policy associated with this service.
​
teams
TeamReference[]
List of teams associated with the service.

​
Example Usage

Update service PSERVICE1 to use escalation policy PEPOLICY456

​
Example Request

{
  "service_id": "PSERVICE1",
  "service_data": {
    "service": {
      "name": "Production API Service v2",
      "description": "Updated REST API service with improved monitoring",
      "escalation_policy": {
        "id": "PEPOLICY456"
      },
      "teams": [
        {
          "id": "PTEAM1"
        },
        {
          "id": "PTEAM2"
        }
      ]
    }
  }
}

​
Example Response

{
  "id": "PSERVICE1",
  "type": "service",
  "name": "Production API Service v2",
  "description": "Updated REST API service with improved monitoring",
  "escalation_policy": {
    "id": "PEPOLICY456",
    "type": "escalation_policy_reference",
    "summary": "Updated Escalation Policy"
  },
  "teams": [
    {
      "id": "PTEAM1",
      "type": "team_reference",
      "summary": "Backend Engineering"
    },
    {
      "id": "PTEAM2",
      "type": "team_reference",
      "summary": "DevOps Team"
    }
  ]
}

​
Important Notes

Escalation Policy Reference: When updating a service, the escalation_policy reference only requires the id field. The summary field is server-generated and will be ignored if you provide it.Example: {"id": "PEPOLICY456"}
Before updating a service, ensure that:
  • The service ID exists and is valid
  • The escalation policy ID exists and is valid
  • Any team IDs you reference exist in your account
  • You have the necessary permissions to update services
  • Active incidents on this service may be affected by escalation policy changes
Update Behavior: The update operation replaces the entire service configuration. Make sure to include all fields you want to keep, not just the ones you want to change.

list_services

List all services

get_service

View current service details

create_service

Create a new service

list_escalation_policies

Find escalation policy IDs

Build docs developers (and LLMs) love

Get started for freeTalk to us