Skip to main content
Glama
us-all

datadog-mcp-server

by us-all

list-users

Retrieve Datadog organization users with support for filtering by name, status, and sorting. Pagination allows efficient browsing of large user lists.

Instructions

List Datadog organization users with filtering and pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageSizeNoNumber of results per page (default 50)
pageNumberNoPage number (0-based)
filterNoSearch filter string. Example: john
filterStatusNoFilter by user status. Example: Active, Pending, Disabled
sortNoSort field. Example: name, email, created_at
sortDirNoSort direction: asc or desc
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. It mentions filtering and pagination but fails to disclose whether the tool is read-only, requires authentication, rate limits, or if it returns deleted users. The description is too sparse 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.

Conciseness5/5

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

The description is a single sentence, concise and front-loaded with verb and resource. Every word serves a purpose with no redundancy.

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 100% schema coverage and no output schema, the description provides the basic purpose and key features. However, it lacks context on safety (read-only), data recency, or scope (e.g., only human users?), which would improve completeness for an agent.

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 input schema has 100% description coverage, so the schema already explains each parameter thoroughly. The description adds no additional semantic nuance beyond summarizing 'filtering and pagination.' Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (List), resource (Datadog organization users), and key features (filtering and pagination). It distinguishes from sibling list tools like list-hosts or list-teams by specifying it's for users.

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?

No guidance on when to use this tool vs alternatives like list-teams or list-hosts. The description lacks any 'when-not-to-use' or context for selection among similar list tools.

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

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/us-all/datadog-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server