RecipeMeta Ads
Check the Meta connection's token health
Token debug and health read: scopes granted, expiry, the connection's own vital signs.
IntentWhether the connection itself is about to fail, before it does.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Connection behaving oddly.
- Scheduled hygiene.
Do not use it when
- No specific contraindication beyond the preconditions below.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Debug the token: scopes, expiry, validity.
Run the health check.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
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 every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- A valid token with missing scopes fails only on specific calls: 'it connects' proves little.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.