# `resident_directory_search`

**Search resident directory.** Finds people in a community by name, email or unit.

**Who can use it:** Owners and managers.

| Scope | Effect | Hints |
|---|---|---|
| `people:read` | read | reads only, idempotent |

## Description shown to assistants

> Use this when a manager or owner asks to find residents by unit, name, or email.

## Arguments

| Argument | Type | Required | About |
|---|---|---|---|
| `property_id` | string | No | The community's public id (`prop_web…`). Pass it on every call. |
| `query` | string | No | Part of a name, email address or unit. |
| `limit` | integer | No | How many to return. From 1 to 100. |

## What it returns

Every result has `content` (one short sentence for the person) and `structuredContent` (the data below). A tool that could not run answers with `isError: true` and a sentence saying why; see [Errors and limits](/developers/mcp/errors-and-limits).

- `query`: the words searched for.
- `residents`: each with `user_id`, `name`, `email`, `role` and `unit`.

`structuredContent` follows this JSON Schema, also in `tools/list` as `outputSchema`:

```json
{
  "type": "object",
  "properties": {
    "property": {
      "type": "object",
      "properties": {
        "id": { "type": "string" },
        "name": { "type": "string" },
        "addressLine1": { "type": ["string", "null"] },
        "addressLine2": { "type": ["string", "null"] },
        "city": { "type": ["string", "null"] },
        "state": { "type": ["string", "null"] },
        "postalCode": { "type": ["string", "null"] },
        "timezone": { "type": ["string", "null"] },
        "billingFrequency": { "type": ["string", "null"] },
        "demoClone": { "type": "boolean" },
        "demoPersona": { "type": ["string", "null"] },
        "demoExpiresAt": { "type": ["string", "null"] }
      },
      "required": ["id", "name"]
    },
    "query": { "type": ["string", "null"] },
    "residents": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "user_id": { "type": ["string", "null"] },
          "name": { "type": ["string", "null"] },
          "email": { "type": ["string", "null"] },
          "role": { "type": "string" },
          "unit": { "type": ["string", "null"] }
        },
        "required": ["role"]
      }
    }
  },
  "required": ["property", "residents"]
}
```

## Notes

- `query` matches part of an email address, first name, last name or unit name, ignoring case. Without it, members are listed.
- `limit` defaults to 25, at most 100.

## Example

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "resident_directory_search",
    "arguments": {
      "property_id": "prop_web4k2m9q7x1v8c3n5b6z0a2s4d",
      "query": "14"
    }
  }
}
```