Skip to main content
Glama
brukhabtu

Datadog MCP Server

by brukhabtu

ListSpansGet

Retrieve and paginate spans matching a search query with specified filters, timestamps, and sorting. Supports date-time ISO8601 and date math for precise span retrieval.

Instructions

List endpoint returns spans that match a span search query. .

Use this endpoint to see your latest spans. This endpoint is rate limited to 300 requests per hour.

Query Parameters:

  • filter[query]: Search query following spans syntax.

  • filter[from]: Minimum timestamp for requested spans. Supports date-time ISO8601, date math, and regular timestamps (milliseconds).

  • filter[to]: Maximum timestamp for requested spans. Supports date-time ISO8601, date math, and regular timestamps (milliseconds).

  • sort: Order of spans in results.

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

  • page[limit]: Maximum number of spans in the response.

Responses:

  • 200 (Success): OK

    • Content-Type: application/json

    • Response Properties:

      • data: Array of spans matching the request.

    • 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": [
    "unknown_type"
  ]
}
  • 403: Forbidden: Access denied.

    • Content-Type: application/json

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "unknown_type"
  ]
}
  • 422: Unprocessable Entity.

    • Content-Type: application/json

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "unknown_type"
  ]
}
  • 429: Too many requests: The rate limit set by the API has been exceeded.

    • Content-Type: application/json

    • Response Properties:

      • errors: A list of errors.

    • Example:

{
  "errors": [
    "unknown_type"
  ]
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filter[from]NoMinimum timestamp for requested spans. Supports date-time ISO8601, date math, and regular timestamps (milliseconds).
filter[query]NoSearch query following spans syntax.
filter[to]NoMaximum timestamp for requested spans. Supports date-time ISO8601, date math, and regular timestamps (milliseconds).
page[cursor]NoList following results with a cursor provided in the previous query.
page[limit]NoMaximum number of spans in the response.
sortNoSort parameters when querying spans.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoArray of spans matching the request.
metaNo
linksNo
Behavior4/5

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

With no annotations provided, the description carries the full burden. It effectively discloses key behavioral traits: it mentions pagination ('Results are paginated'), rate limiting ('rate limited to 300 requests per hour'), and includes HTTP response codes (200, 400, 403, 422, 429) with examples. However, it lacks details on authentication needs, data format specifics beyond JSON, or error handling nuances, preventing a score of 5.

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 key information (purpose, pagination, usage, rate limits), but it becomes verbose with redundant parameter and response details that are already covered in the schema and output schema. The inclusion of extensive HTTP response examples and markdown links adds bulk without proportional value, 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 tool's complexity (6 parameters, pagination, rate limits) and the presence of an output schema (implied by response details), the description is mostly complete. It covers purpose, behavior, parameters, and responses adequately. However, it could improve by linking to sibling tools or providing more context on the 'spans syntax' mentioned, keeping it from a perfect score.

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%, so the input schema already documents all parameters thoroughly. The description repeats parameter details in a 'Query Parameters' section, adding minimal value beyond the schema. This meets the baseline of 3, as the schema does the heavy lifting, but the description doesn't provide additional context like default behaviors or usage examples for parameters.

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: 'List endpoint returns spans that match a span search query.' It specifies the verb ('list'/'returns') and resource ('spans'), and distinguishes it from other list tools by focusing on spans. However, it doesn't explicitly differentiate from sibling tools like 'ListLogsGet' or 'ListSpansMetrics', which might handle similar data types, so it doesn't reach a perfect 5.

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 some usage context: 'Use this endpoint to see your latest spans.' This implies it's for recent data, but it doesn't offer explicit guidance on when to use this tool versus alternatives (e.g., 'ListLogsGet' for logs or 'ListSpansMetrics' for metrics). No exclusions or prerequisites are mentioned, leaving usage somewhat implied rather than clearly defined.

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