<!-- enhance-docs page=reference/mcp/person-recipients-recent -->
<!-- enhance-docs release-sha256=7ff3d88e90f9dd4fa5ee87960f993597885d25e92abc5665bd2ecbc70cd6621b -->

# person.recipients.recent

<span class="reference-badge">query</span> <span class="reference-badge">read</span>

Use when current person state is missing from the task context.

## Before calling

- Authenticate as the accountable Enhance person.
- Use only resource identifiers returned by an earlier capability result or supplied by the person.

## Input

<details class="reference-schema">
<summary>Show complete JSON Schema</summary>

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "type": "object",
 "properties": {},
 "additionalProperties": false
}
```
</details>

### Example

<details class="reference-schema">
<summary>Show example input</summary>

```json
{}
```
</details>

## Result

Returns a typed person.recipients.recent result from the Enhance API without transport-specific prose.

## Recovery

- BAD_REQUEST: correct the named fields and call again.
- UNAUTHORIZED: restore Enhance authentication, then retry once.
- FORBIDDEN or NOT_FOUND: check the supplied resource and selection; do not substitute unrelated content. Ask for corrected access or scope if needed.
- CONFLICT: read the current resource, merge the intended change, and retry with its version.
- INTERNAL: run Enhance diagnostics, report the failure, and stop repeating the call.

## Continue with

- Use the returned identifiers and version in the next person operation.

Compatibility: `25350100a4eb6afa92d8a28a560a4edf8166cf211eb418263c263cc6adde27f2`.
