Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

ListAPIKeys

Retrieve and manage all API keys for your account with customizable filters, sorting, and pagination options to streamline access control.

Instructions

List all API keys available for your account.

Query Parameters:

  • page[size]: Size for a given page. The maximum allowed value is 100.

  • page[number]: Specific page number to return.

  • sort: API key attribute used to sort results. Sort order is ascending by default. In order to specify a descending sort, prefix the attribute with a minus sign.

  • filter: Filter API keys by the specified string.

  • filter[created_at][start]: Only include API keys created on or after the specified date.

  • filter[created_at][end]: Only include API keys created on or before the specified date.

  • filter[modified_at][start]: Only include API keys modified on or after the specified date.

  • filter[modified_at][end]: Only include API keys modified on or before the specified date.

  • include: Comma separated list of resource paths for related resources to include in the response. Supported resource paths are created_by and modified_by.

  • filter[remote_config_read_enabled]: Filter API keys by remote config read enabled status.

  • filter[category]: Filter API keys by category.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

      • data: Array of API keys.

      • included: Array of objects related to the API key.

    • Example:

{
  "data": [
    "unknown_type"
  ],
  "included": [
    "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
filterNoFilter API keys by the specified string.
filter[category]NoFilter API keys by category.
filter[created_at][end]NoOnly include API keys created on or before the specified date.
filter[created_at][start]NoOnly include API keys created on or after the specified date.
filter[modified_at][end]NoOnly include API keys modified on or before the specified date.
filter[modified_at][start]NoOnly include API keys modified on or after the specified date.
filter[remote_config_read_enabled]NoFilter API keys by remote config read enabled status.
includeNoComma separated list of resource paths for related resources to include in the response. Supported resource paths are `created_by` and `modified_by`.
page[number]NoSpecific page number to return.
page[size]NoSize for a given page. The maximum allowed value is 100.
sortNoSorting optionsname

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoArray of API keys.
metaNo
includedNoArray of objects related to the API key.

Tool Definition Quality

B3.1/5.0
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 includes response codes (200, 400, 403, 429) and examples, which adds context beyond basic listing, but doesn't cover permissions, rate limits, or mutation risks. It's adequate but has gaps for a tool with no annotations.

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 long and redundant, with extensive parameter and response sections that duplicate the schema. It's not front-loaded; the core purpose is stated upfront but buried in verbose details. Sentences like the parameter listings don't earn their place, reducing efficiency.

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 (11 parameters, no annotations, output schema exists), the description is fairly complete. It covers purpose, parameters, and responses, and with an output schema, it doesn't need to explain return values in detail. However, it could better address usage context and behavioral traits.

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 repeats parameter details verbatim from the schema, adding no extra meaning or context. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 'List all API keys available for your account,' which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'ListApplicationKeys' or 'ListUsers,' which are also list operations for different resources, so it misses full sibling differentiation.

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, such as filtering or pagination scenarios, or how it relates to other list tools in the sibling set. It lacks explicit context, exclusions, or named alternatives, leaving usage unclear.

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