Reference
Recommend, approve, execute, verify
The plugin instructions default to recommend-then-execute and require explicit user approval before actions that create or change spend.
Before approving
- Identity: verify the Synter organization and exact platform account ID returned by the tools.
- Economics: verify currency, daily/total budget, bid strategy, CPA/ROAS target, and scaling step.
- Measurement: verify the intended conversion action, GA4/pixel/CAPI state, and destination URL before spending.
- Scope: identify the exact campaign, audience, creative, fields, and old/new values.
- Evidence: distinguish observed data, assumptions, recommendations, drafts, and executed changes.
After an action
- Re-read the account to confirm the requested change landed on the intended object.
- Report real campaign/ad IDs and the current status.
- Do not equate “created” with enabled, approved, delivering, or producing impressions.
- Check post-action budget, targeting, conversion attachment, URL, and delivery state.
Secrets and plugin trust
Never paste a Synter API key, platform credential, access token, customer list, or other secret into a prompt. Configure the key in the sensitive plugin field or, for MCP clients that support custom headers, as X-Synter-Key. Standalone Claude Custom Connector UI cannot set arbitrary HTTP headers. Install only from the canonical repository or an organization-reviewed package; plugins can include connectors and local components with meaningful permissions.
Unattended operation
The repository's headless SDK harness is read-only by default. Do not enable unattended writes merely because a workflow can execute them interactively. Apply separate operational controls, narrow credentials, spending limits, monitoring, and incident procedures for any automation.