Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

ListLogsCustomDestinations

Retrieve a list of configured custom log destinations and their definitions within your Datadog organization. Simplify log management by accessing structured JSON responses for efficient integration and monitoring.

Instructions

Get the list of configured custom destinations in your organization with their definitions.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

      • data: A list of custom destinations.

    • Example:

{
  "data": [
    "unknown_type"
  ]
}
  • 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

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoA list of custom destinations.
Behavior2/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 of behavioral disclosure. It mentions HTTP response codes (200, 403, 429) and examples, which adds some context about success and error conditions. However, it lacks critical details such as whether this is a read-only operation, authentication requirements, rate limits, pagination behavior, or what 'custom destinations' entail in practice. For a tool with zero annotation coverage, this is insufficient.

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

Conciseness3/5

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

The description is front-loaded with the core purpose, but it includes extensive HTTP response details that may be redundant if an output schema exists (context signals indicate 'Has output schema: true'). The response examples and error codes add length without necessarily earning their place, making it somewhat verbose for a simple list operation.

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 simplicity (0 parameters, output schema present), the description covers the basic purpose and response formats adequately. However, with no annotations and sibling tools present, it misses opportunities to clarify behavioral traits (e.g., read-only nature, organizational scope) and usage distinctions, leaving gaps in contextual understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on responses. This meets expectations for a parameterless tool, though it doesn't add extra semantic value beyond the schema.

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 the list of configured custom destinations in your organization with their definitions.' It specifies the verb ('Get'), resource ('custom destinations'), and scope ('in your organization'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'GetLogsCustomDestination' (singular vs. plural), which prevents a perfect score.

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 sibling tools like 'GetLogsCustomDestination' for retrieving a single destination, nor does it specify prerequisites, contexts, or exclusions for usage. This leaves the agent without direction on tool selection.

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