GetLogsCustomDestination

Retrieve specific custom destination details from Datadog MCP Server using a unique ID. Streamline access to log configurations and handle errors efficiently.

Instructions

Get a specific custom destination in your organization.

Path Parameters:

custom_destination_id (Required): The ID of the custom destination.

Responses:

200 (Success): OK
- Content-Type: application/json
- Response Properties:
- Example:

{
  "data": "unknown_type"
}

400: Bad Request
- 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	Default
`custom_destination_id`	Yes	The ID of the custom destination.

Input Schema (JSON Schema)

{
  "properties": {
    "custom_destination_id": {
      "description": "The ID of the custom destination.",
      "type": "string"
    }
  },
  "required": [
    "custom_destination_id"
  ],
  "type": "object"
}

You must be authenticated.

Datadog MCP Server

GetLogsCustomDestination

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from Datadog MCP Server

Related Tools

MCP directory API