GetHistoricalCostByOrg

Retrieve historical cost data for multi-org or single root-org accounts in Datadog MCP. Specify time range and view to analyze costs at parent-org or sub-org levels. Includes options for connected accounts.

Instructions

Get historical cost across multi-org and single root-org accounts. Cost data for a given month becomes available no later than the 16th of the following month.

This endpoint is only accessible for parent-level organizations.

Query Parameters:

view: String to specify whether cost is broken down at a parent-org level or at the sub-org level. Available views are summary and sub-org. Defaults to summary.
start_month (Required): Datetime in ISO-8601 format, UTC, precise to month: [YYYY-MM] for cost beginning this month.
end_month: Datetime in ISO-8601 format, UTC, precise to month: [YYYY-MM] for cost ending this month.
include_connected_accounts: Boolean to specify whether to include accounts connected to the current account as partner customers in the Datadog partner network program. Defaults to false.

Responses:

200 (Success): OK
- Content-Type: application/json;datetime-format=rfc3339
- Response Properties:
  - data: Response containing Chargeback Summary.
- Example:

{
  "data": [
    "unknown_type"
  ]
}

400: Bad Request
- Content-Type: application/json;datetime-format=rfc3339
- Response Properties:
  - errors: A list of errors.
- Example:

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

403: Forbidden - User is not authorized
- Content-Type: application/json;datetime-format=rfc3339
- Response Properties:
  - errors: A list of errors.
- Example:

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

429: Too many requests
- Content-Type: application/json;datetime-format=rfc3339
- Response Properties:
  - errors: A list of errors.
- Example:

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

Input Schema

Name	Required	Description
`end_month`	No	Datetime in ISO-8601 format, UTC, precise to month: `[YYYY-MM]` for cost ending this month.
`include_connected_accounts`	No	Boolean to specify whether to include accounts connected to the current account as partner customers in the Datadog partner network program. Defaults to `false`.
`start_month`	Yes	Datetime in ISO-8601 format, UTC, precise to month: `[YYYY-MM]` for cost beginning this month.
`view`	No	String to specify whether cost is broken down at a parent-org level or at the sub-org level. Available views are `summary` and `sub-org`. Defaults to `summary`.

Input Schema (JSON Schema)

{
  "properties": {
    "end_month": {
      "description": "Datetime in ISO-8601 format, UTC, precise to month: `[YYYY-MM]` for cost ending this month.",
      "format": "date-time",
      "type": "string"
    },
    "include_connected_accounts": {
      "default": false,
      "description": "Boolean to specify whether to include accounts connected to the current account as partner customers in the Datadog partner network program. Defaults to `false`. ",
      "type": "boolean"
    },
    "start_month": {
      "description": "Datetime in ISO-8601 format, UTC, precise to month: `[YYYY-MM]` for cost beginning this month.",
      "format": "date-time",
      "type": "string"
    },
    "view": {
      "description": "String to specify whether cost is broken down at a parent-org level or at the sub-org level. Available views are `summary` and `sub-org`.  Defaults to `summary`.",
      "type": "string"
    }
  },
  "required": [
    "start_month"
  ],
  "type": "object"
}

Datadog MCP Server

GetHistoricalCostByOrg

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from Datadog MCP Server

Related Tools

MCP directory API