Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

GetHourlyUsage

Retrieve hourly usage data for specific Datadog product families by specifying start and end timestamps, product families, and optional breakdowns to monitor and analyze usage trends effectively.

Instructions

Get hourly usage by product family.

Query Parameters:

  • filter[timestamp][start] (Required): Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage beginning at this hour.

  • filter[timestamp][end]: Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage ending before this hour.

  • filter[product_families] (Required): Comma separated list of product families to retrieve. Available families are all, analyzed_logs, application_security, audit_trail, serverless, ci_app, cloud_cost_management, cloud_siem, csm_container_enterprise, csm_host_enterprise, cspm, custom_events, cws, dbm, error_tracking, fargate, infra_hosts, incident_management, indexed_logs, indexed_spans, ingested_spans, iot, lambda_traced_invocations, logs, network_flows, network_hosts, network_monitoring, observability_pipelines, online_archive, profiling, rum, rum_browser_sessions, rum_mobile_sessions, sds, snmp, software_delivery, synthetics_api, synthetics_browser, synthetics_mobile, synthetics_parallel_testing, timeseries, vuln_management, and workflow_executions. The following product family has been deprecated: audit_logs.

  • filter[include_descendants]: Include child org usage in the response. Defaults to false.

  • filter[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.

  • filter[include_breakdown]: Include breakdown of usage by subcategories where applicable (for product family logs only). Defaults to false.

  • filter[versions]: Comma separated list of product family versions to use in the format product_family:version. For example, infra_hosts:1.0.0. If this parameter is not used, the API will use the latest version of each requested product family. Currently all families have one version 1.0.0.

  • page[limit]: Maximum number of results to return (between 1 and 500) - defaults to 500 if limit not specified.

  • page[next_record_id]: List following results with a next_record_id provided in the previous query.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json;datetime-format=rfc3339

    • Response Properties:

      • data: Response containing hourly usage.

    • Example:

{
  "data": [
    "unknown_type"
  ],
  "meta": "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

TableJSON Schema
NameRequiredDescriptionDefault
filter[include_breakdown]NoInclude breakdown of usage by subcategories where applicable (for product family logs only). Defaults to false.
filter[include_connected_accounts]NoBoolean to specify whether to include accounts connected to the current account as partner customers in the Datadog partner network program. Defaults to false.
filter[include_descendants]NoInclude child org usage in the response. Defaults to false.
filter[product_families]YesComma separated list of product families to retrieve. Available families are `all`, `analyzed_logs`, `application_security`, `audit_trail`, `serverless`, `ci_app`, `cloud_cost_management`, `cloud_siem`, `csm_container_enterprise`, `csm_host_enterprise`, `cspm`, `custom_events`, `cws`, `dbm`, `error_tracking`, `fargate`, `infra_hosts`, `incident_management`, `indexed_logs`, `indexed_spans`, `ingested_spans`, `iot`, `lambda_traced_invocations`, `logs`, `network_flows`, `network_hosts`, `network_monitoring`, `observability_pipelines`, `online_archive`, `profiling`, `rum`, `rum_browser_sessions`, `rum_mobile_sessions`, `sds`, `snmp`, `software_delivery`, `synthetics_api`, `synthetics_browser`, `synthetics_mobile`, `synthetics_parallel_testing`, `timeseries`, `vuln_management`, and `workflow_executions`. The following product family has been **deprecated**: `audit_logs`.
filter[timestamp][end]NoDatetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage ending **before** this hour.
filter[timestamp][start]YesDatetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage beginning at this hour.
filter[versions]NoComma separated list of product family versions to use in the format `product_family:version`. For example, `infra_hosts:1.0.0`. If this parameter is not used, the API will use the latest version of each requested product family. Currently all families have one version `1.0.0`.
page[limit]NoMaximum number of results to return (between 1 and 500) - defaults to 500 if limit not specified.
page[next_record_id]NoList following results with a next_record_id provided in the previous query.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoResponse containing hourly usage.
metaNo
Behavior3/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 partially succeeds by documenting query parameters and response codes (200, 400, 403, 429), which helps the agent understand input/output behavior and error conditions. However, it lacks critical behavioral details like rate limits, authentication requirements, pagination mechanics beyond 'page[next_record_id]', or whether this is a read-only operation (though 'Get' implies it).

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

Conciseness2/5

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

The description is overly verbose and poorly structured. It front-loads the purpose but then duplicates the entire parameter documentation from the schema, followed by lengthy response details. This creates redundancy and makes it harder to scan. The response examples with 'unknown_type' placeholders add little value. A more concise approach would focus on unique insights not in the schema.

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 tool's complexity (9 parameters, 2 required) and the presence of an output schema (implied by response documentation), the description is moderately complete. It covers parameters and responses but lacks context about the tool's role in the broader system (e.g., how it relates to sibling usage tools). The output schema existence reduces the need to explain return values, but the description could better integrate with the structured data.

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?

The schema description coverage is 100%, meaning all parameters are already documented in the input schema. The description repeats this parameter information verbatim, adding no additional semantic context beyond what's in the schema. This meets the baseline of 3 since the schema does the heavy lifting, but the description doesn't provide extra value like usage examples or edge cases.

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: 'Get hourly usage by product family.' It specifies the verb ('Get') and resource ('hourly usage by product family'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'GetUsageApplicationSecurityMonitoring' or 'GetUsageLambdaTracedInvocations', which appear to be more specific variants.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, context for usage, or comparisons with sibling tools. The only implicit usage hint is the parameter documentation, but there's no explicit 'when-to-use' or 'when-not-to-use' information.

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