RecipeTikTok Ads
Probe any TikTok read endpoint safely
The generic read endpoint, for exploration without tokens in the clear.
IntentA GET passthrough for reads the catalogue has not packaged yet.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- API exploration.
- Verifying a hypothesis before requesting a packaged tool.
Do not use it when
- Writes: this is read-only by design, and that is the point.
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.
Call the read endpoint with the documented path and params.
Record the response shape for the future packaged version.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
The endpoint answers with paginated data
Conclude
Walk pages explicitly: a first-page read presented as complete is silent truncation.
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.
- Undocumented params fail silently on some endpoints: absence of error is not proof of effect.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.