ListIncidentServices

Retrieve all incident services for an organization with options to include related users, filter by name, and paginate results for efficient management.

Instructions

Get all incident services uploaded for the requesting user's organization. If the include[users] query parameter is provided, the included attribute will contain the users related to these incident services.

Query Parameters:

include: Specifies which types of related objects should be included in the response.
page[size]: Size for a given page. The maximum allowed value is 100.
page[offset]: Specific offset to use as the beginning of the returned page.
filter: A search query that filters services by name.

Responses:

200 (Success): OK
- Content-Type: application/json
- Response Properties:
  - data: An array of incident services.
  - included: Included related resources which the user requested.
- Example:

{
  "data": [
    {
      "id": "00000000-0000-0000-0000-000000000000",
      "type": "services"
    }
  ],
  "included": [
    "unknown_type"
  ],
  "meta": "unknown_type"
}

400: Bad Request
- Content-Type: application/json
- Response Properties:
  - errors: A list of errors.
- Example:

{
  "errors": [
    "Bad Request"
  ]
}

401: Unauthorized
- Content-Type: application/json
- Response Properties:
  - errors: A list of errors.
- Example:

{
  "errors": [
    "Bad Request"
  ]
}

403: Forbidden
- Content-Type: application/json
- Response Properties:
  - errors: A list of errors.
- Example:

{
  "errors": [
    "Bad Request"
  ]
}

404: Not Found
- Content-Type: application/json
- Response Properties:
  - errors: A list of errors.
- Example:

{
  "errors": [
    "Bad Request"
  ]
}

429: Too many requests
- Content-Type: application/json
- Response Properties:
  - errors: A list of errors.
- Example:

{
  "errors": [
    "Bad Request"
  ]
}

Input Schema

Name	Required	Description
`filter`	No	A search query that filters services by name.
`include`	No	Object related to an incident.
`page[offset]`	No	Specific offset to use as the beginning of the returned page.
`page[size]`	No	Size for a given page. The maximum allowed value is 100.

Input Schema (JSON Schema)

{
  "properties": {
    "filter": {
      "description": "A search query that filters services by name.",
      "example": "ExampleServiceName",
      "type": "string"
    },
    "include": {
      "description": "Object related to an incident.",
      "enum": [
        "users",
        "attachments"
      ],
      "type": "string",
      "x-enum-varnames": [
        "USERS",
        "ATTACHMENTS"
      ]
    },
    "page[offset]": {
      "default": 0,
      "description": "Specific offset to use as the beginning of the returned page.",
      "example": 0,
      "format": "int64",
      "type": "integer"
    },
    "page[size]": {
      "default": 10,
      "description": "Size for a given page. The maximum allowed value is 100.",
      "example": 10,
      "format": "int64",
      "type": "integer"
    }
  },
  "required": [],
  "type": "object"
}

Datadog MCP Server

ListIncidentServices

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from Datadog MCP Server

Related Tools

MCP directory API