Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

ListTagConfigurations

Retrieve and filter metrics with configured tags in Datadog, enabling precise control over metric tag configurations for observability and analytics.

Instructions

Returns all metrics that can be configured in the Metrics Summary page or with Metrics without Limits™ (matching additional filters if specified). Optionally, paginate by using the page[cursor] and/or page[size] query parameters. To fetch the first page, pass in a query parameter with either a valid page[size] or an empty cursor like page[cursor]=. To fetch the next page, pass in the next_cursor value from the response as the new page[cursor] value. Once the meta.pagination.next_cursor value is null, all pages have been retrieved.

Query Parameters:

  • filter[configured]: Filter custom metrics that have configured tags.

  • filter[tags_configured]: Filter tag configurations by configured tags.

  • filter[metric_type]: Filter metrics by metric type.

  • filter[include_percentiles]: Filter distributions with additional percentile aggregations enabled or disabled.

  • filter[queried]: (Preview) Filter custom metrics that have or have not been queried in the specified window[seconds]. If no window is provided or the window is less than 2 hours, a default of 2 hours will be applied.

  • filter[tags]: Filter metrics that have been submitted with the given tags. Supports boolean and wildcard expressions. Can only be combined with the filter[queried] filter.

  • filter[related_assets]: (Preview) Filter metrics that are used in dashboards, monitors, notebooks, SLOs.

  • window[seconds]: The number of seconds of look back (from now) to apply to a filter[tag] or filter[queried] query. Default value is 3600 (1 hour), maximum value is 2,592,000 (30 days).

  • page[size]: Maximum number of results returned.

  • page[cursor]: String to query the next page of results. This key is provided with each valid response from the API in meta.pagination.next_cursor. Once the meta.pagination.next_cursor key is null, all pages have been retrieved.

Responses:

  • 200 (Success): Success

    • Content-Type: application/json

    • Response Properties:

      • data: Array of metrics and metric tag configurations.

    • Example:

{
  "data": [
    "unknown_type"
  ],
  "links": "unknown_type",
  "meta": "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"
  ]
}
  • 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[configured]NoFilter custom metrics that have configured tags.
filter[include_percentiles]NoFilter distributions with additional percentile aggregations enabled or disabled.
filter[metric_type]NoThe metric's type category.distribution
filter[queried]No(Preview) Filter custom metrics that have or have not been queried in the specified window[seconds]. If no window is provided or the window is less than 2 hours, a default of 2 hours will be applied.
filter[related_assets]No(Preview) Filter metrics that are used in dashboards, monitors, notebooks, SLOs.
filter[tags]NoFilter metrics that have been submitted with the given tags. Supports boolean and wildcard expressions. Can only be combined with the filter[queried] filter.
filter[tags_configured]NoTag keys to filter by.
page[cursor]NoString to query the next page of results. This key is provided with each valid response from the API in `meta.pagination.next_cursor`. Once the `meta.pagination.next_cursor` key is null, all pages have been retrieved.
page[size]NoMaximum number of results returned.
window[seconds]NoThe number of seconds of look back (from now) to apply to a filter[tag] or filter[queried] query. Default value is 3600 (1 hour), maximum value is 2,592,000 (30 days).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoArray of metrics and metric tag configurations.
metaNo
linksNo
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses pagination behavior, filtering options, and preview features, which is helpful. However, it lacks details on permissions, rate limits, or side effects (though 'Returns' suggests read-only). The description doesn't contradict any annotations, as there are none.

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 mixes tool purpose, usage instructions, parameter details, and HTTP response examples in a single block. The front-loaded purpose is clear, but subsequent sections (e.g., detailed query parameters and response examples) are redundant with the schema and output schema, making it unnecessarily long and cluttered.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (10 parameters, no annotations, output schema exists), the description is fairly complete. It covers the tool's purpose, filtering, pagination, and includes response examples, though some details (like error handling) are redundant with the output schema. The output schema reduces the need for return value explanation, but the description still adds useful context.

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 thoroughly. The description adds minimal value beyond the schema by briefly mentioning pagination parameters and filtering, but it doesn't provide additional context or examples not covered in the schema. Baseline 3 is appropriate given high schema coverage.

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: 'Returns all metrics that can be configured in the Metrics Summary page or with Metrics without Limits™ (matching additional filters if specified).' It specifies the resource (metrics with tag configurations) and the action (returns/list). However, it doesn't explicitly differentiate from sibling tools like 'ListActiveMetricConfigurations' or 'ListTagConfigurationByName', which appear related.

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

Usage Guidelines3/5

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

The description provides implied usage guidance by mentioning pagination and filtering capabilities, but it doesn't explicitly state when to use this tool versus alternatives. For example, it doesn't compare with 'ListActiveMetricConfigurations' or 'ListTagConfigurationByName' from the sibling list, leaving the agent to infer based on the tool name and description.

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