Skip to main content
Glama
us-all

datadog-mcp-server

list-users

Read-only

Retrieve Datadog organization users with filtering by name, status, and pagination controls for efficient user management.

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?

Annotations already indicate readOnlyHint and openWorldHint. The description adds no additional behavioral context beyond what is already in the schema, such as rate limits, default ordering, or response handling.

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

Conciseness4/5

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

The description is a single concise sentence that front-loads the purpose, but it is slightly under-specified for a tool with 6 parameters.

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?

With no output schema and 6 optional parameters, the description could be more complete. It does not explain default behavior or what the response contains.

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 coverage is 100%, so the description's mention of 'filtering and pagination' adds no new parameter meaning beyond what the schema already provides.

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 tool lists Datadog organization users with filtering and pagination, with a specific verb and resource. It distinguishes from sibling tools that list other entities.

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 implies usage for listing users with filters and pagination but provides no explicit guidance on when to use it over alternative tools or when not to use it.

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