ListIncidentAttachments

Retrieve all attachments for a specific incident by providing its UUID, with options to filter by attachment type and include related resources in the response. Simplifies access to critical incident data within Datadog’s observability platform.

Instructions

Get all attachments for a given incident.

Path Parameters:

incident_id (Required): The UUID of the incident.

Query Parameters:

include: Specifies which types of related objects are included in the response.
filter[attachment_type]: Specifies which types of attachments are included in the response.

Responses:

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

{
  "data": [
    {
      "attributes": {
        "attachment": {
          "documentUrl": "",
          "title": "Postmortem IR-123"
        },
        "attachment_type": "postmortem"
      },
      "id": "00000000-abcd-0002-0000-000000000000",
      "relationships": {
        "last_modified_by_user": {
          "data": {
            "id": "00000000-0000-0000-cccc-000000000000",
            "type": "users"
          }
        }
      },
      "type": "incident_attachments"
    }
  ],
  "included": [
    "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[attachment_type]`	No	Specifies which types of attachments are included in the response.
`incident_id`	Yes	The UUID of the incident.
`include`	No	Specifies which types of related objects are included in the response.

Input Schema (JSON Schema)

{
  "$defs": {
    "IncidentAttachmentAttachmentType": {
      "description": "The type of the incident attachment attributes.",
      "enum": [
        "link",
        "postmortem"
      ],
      "example": "link",
      "type": "string",
      "x-enum-varnames": [
        "LINK",
        "POSTMORTEM"
      ]
    },
    "IncidentAttachmentRelatedObject": {
      "description": "The object related to an incident attachment.",
      "enum": [
        "users"
      ],
      "type": "string",
      "x-enum-varnames": [
        "USERS"
      ]
    }
  },
  "properties": {
    "filter[attachment_type]": {
      "description": "Specifies which types of attachments are included in the response.",
      "items": {
        "$ref": "#/$defs/IncidentAttachmentAttachmentType"
      },
      "type": "array"
    },
    "incident_id": {
      "description": "The UUID of the incident.",
      "type": "string"
    },
    "include": {
      "description": "Specifies which types of related objects are included in the response.",
      "items": {
        "$ref": "#/$defs/IncidentAttachmentRelatedObject"
      },
      "type": "array"
    }
  },
  "required": [
    "incident_id"
  ],
  "type": "object"
}

Datadog MCP Server

ListIncidentAttachments

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from Datadog MCP Server

Related Tools

MCP directory API