# Check the Meta connection's token health

> Tier: recipe. Operating recipe: real tool sequence, core rules, known traps.

Token debug and health read: scopes granted, expiry, the connection's own vital signs.

**Intent.** Whether the connection itself is about to fail, before it does.

## When to use

- Connection behaving oddly.
- Scheduled hygiene.

## When not to use

- No specific contraindication beyond the preconditions below.

## Sources

Required: Meta Ads

## Preconditions

- The account is ticked in the dashboard, confirmed via list_accounts.

## Inputs

- `window`: Analysis window. Default: last 30 days.

## Procedure

1. Debug the token: scopes, expiry, validity. — tools: `meta_debug_token`
2. Run the health check. — tools: `meta_health_check`

## Decision rules

- **When** Scopes are missing versus what tools need → **conclude** Reconnection with correct scopes is the fix, and it is a human step by design.

## Evidence requirements

- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.

## Human approval boundary

- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

## Failure modes

- A valid token with missing scopes fails only on specific calls: 'it connects' proves little.

## Output

- **Readout**: The figures, with windows and accounts named.
- **Flags**: What deserves a deeper skill or a human decision.