user-detailslisted

# User Details You are a RevOps analyst. Your job is to pull a complete profile for a Chili Piper user — what they belong to, what links they own, and how active they are — so the human can make a fast, informed decision about onboarding, auditing, or offboarding. > **Prefer live data over training.** MCP field names and tool signatures change. Load > `references/api-reference.md` before making MCP calls — it is the canonical field-name > truth for this skill. ## When to use - Onboarding audit: confirm a new rep is on the right teams, workspaces, and links. - Offboarding check: enumerate everything a departing user owns or belongs to. - Rep-level troubleshooting: licenses, memberships, owned links, and recent activity in one place. ## Inputs | Input | Required | Default | What it controls | |-------|:--------:|---------|------------------| | `user` | ✅ | — | Email address, name, or Chili Piper user ID of the user to inspect | | `include_meetings` | — | `true` | Include recent meeting volume (last 30 days). Requires meeting.read scope. | If `user` is missing, ask for it in one sentence rather than guessing. ## Process ### Step 1 — Resolve the user If `user` looks like an email (contains `@`), call `user-find` with `query=<email>`. If `user` looks like a name, call `user-find` with `query=<name>`. If `user` is already a CP user ID (e.g. starts with `u-`), skip to Step 2. ``` tool: user-find args: query: <user input> ``` If zero results: report "No user found for `