Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

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

TableJSON Schema
NameRequiredDescriptionDefault
filter[attachment_type]NoSpecifies which types of attachments are included in the response.
incident_idYesThe UUID of the incident.
includeNoSpecifies which types of related objects are included in the response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesAn array of incident attachments.
includedNoIncluded related resources that the user requested.
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions HTTP responses (e.g., 200, 400, 429) and includes examples, but doesn't clarify if this is a read-only operation, discuss authentication needs, rate limits beyond the 429 error, or detail pagination or data format constraints beyond the example.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose but includes extensive HTTP response details that may be redundant if an output schema exists. While structured with sections, it could be more concise by focusing on value-added information rather than repeating error examples.

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?

Given the complexity (3 parameters, 100% schema coverage, output schema likely present), the description covers basic purpose and parameters but lacks behavioral context like read-only status or usage guidelines. It includes response examples, which helps, but doesn't fully compensate for missing annotations and sibling differentiation.

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 the schema already documents all parameters. The description repeats parameter names and purposes but doesn't add significant meaning beyond the schema, such as explaining how 'include' affects 'included' in responses or providing usage examples for 'filter[attachment_type]'.

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?

The description clearly states the tool's purpose with 'Get all attachments for a given incident,' specifying the verb ('Get') and resource ('attachments'). It distinguishes from siblings like 'GetIncident' or 'SearchIncidents' by focusing on attachments, though it doesn't explicitly compare to them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, such as needing an existing incident, or comparisons to other attachment-related tools, which could be inferred from sibling names but isn't stated.

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

Related 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/brukhabtu/datadog-mcp'

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