An ads agent should be able to prove which account it queried and where its numbers came from before you rely on its recommendations. A useful first task is a small report that you can reproduce in the advertising interface.
Start with one client account, one date range and one question. For example: which campaigns changed spend and conversion volume between two complete seven-day periods?
Establish the reporting target
An agency manager account and a client advertising account serve different purposes. Record the client account identifier explicitly. Include the reporting timezone, currency and the conversion actions that matter to the business. Campaign names are useful labels, but stable campaign IDs make comparisons easier to audit.
Do not let a familiar client name substitute for checking the selected account. If the connector exposes several accounts and the request is ambiguous, the agent should stop and resolve the target before querying.
Give the agent a reproducible task
Use this starting prompt, replacing the account placeholder:
For client account [ID], compare the last seven complete days with the previous seven, using the account timezone. Show campaign IDs, spend, clicks, conversions and conversion-action names. State which fields came from the API and which values you calculated. If a field is unavailable, say so. Do not change anything. For each finding, separate the observed change from possible explanations and list the extra data needed to test them.
Requesting no changes is an instruction, not an access control. Use read-only tools or permissions where the integration supports them. Check the actual permissions of your setup rather than assuming the protocol name establishes them.
Reconcile one campaign
Open the same client account in Google Ads. Match the dates and columns before comparing totals. Check which conversion definition the report uses. A count of form submissions answers a different question from a count of qualified opportunities.
If numbers differ, investigate the account scope, date boundaries, conversion columns and query dimensions first. Do not ask the agent to explain a business trend until the underlying report is consistent. Preserve the original returned rows so that calculated ratios can be checked independently.
A report should show a missing field as unavailable. Replacing an unavailable value with zero can create a convincing but false conclusion.
Separate evidence from an explanation
“Spend increased while conversions fell” describes an observation. “The audience is fatigued” proposes an explanation. The second statement needs additional evidence.
Require a table with three columns: observed change, possible explanation and next check. The next check could involve search terms, conversion tracking, change history or downstream CRM outcomes. The relevant check depends on the account and the data actually available.
This structure makes uncertainty visible without preventing useful analysis. It also gives a human operator a specific investigation to run.
Define what passing means
The first report passes when the account and time period are correct, a sample reconciles with the interface, calculated values are traceable, missing fields are explicit, and no account changes occurred. Save the prompt, returned evidence and test date together.
Only then design a separate workflow for changes. A proposed change should identify the target, current value, requested value and scope of authorization. After an authorized write, read the resource back and compare the accepted state with the request. Do not assume that every operation is reversible.
For a Synter implementation, start with the installation documentation and MCP overview, then confirm the available operations for your connected account. Keep the acceptance test the same regardless of the agent or connector you select.
If your evaluation includes CRM outcomes, keep platform conversions separate from qualified pipeline. The Attio campaign-data guide shows a reproducible join that avoids counting campaign spend once per opportunity.