rapid7-mcp

search_users

Search user accounts monitored by InsightIDR using filters like name, email, domain, or department.

Instructions

Search user accounts monitored by InsightIDR by name, email, domain, or department

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_users"
  }
}

Input Schema

Name	Required	Description
`name`	No	Filter by user display name (partial match)
`size`	No	Number of results to return (1-100)
`email`	No	Filter by email address
`index`	No	Pagination index
`domain`	No	Filter by Active Directory domain
`search`	No	General search across user fields
`disabled`	No	Filter by account disabled status
`department`	No	Filter by department

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description alone must disclose behavioral traits. It only mentions the search capabilities and fields, without covering pagination, response structure, or any side effects. The schema already covers parameters; no new behavioral context is added.

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, clear sentence that efficiently conveys the tool's purpose without unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema, 8 parameters, and no annotations, the description is insufficient. It does not clarify pagination, result format, or the fact that it is a read operation. Richer context is needed for a search tool.

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% (all parameters described in schema). The description mentions only a subset of parameters (name, email, domain, department) but does not add meaning beyond the schema. Baseline score of 3 applies.

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 searches user accounts monitored by InsightIDR using specific fields (name, email, domain, department). It distinguishes from sibling tools like search_assets or search_investigations by focusing on users.

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 searching users by the listed fields but does not explicitly state when to use this tool versus alternatives (e.g., search_assets, search_investigations). No direct comparison or exclusions are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.