Meta Ads connector: what Refresh tools does in Sume

Refresh tools is an admin action on the Meta Ads row that re-runs tool discovery with the grant you already gave. It replaces the saved catalog atomically only after a complete discovery. If the refresh fails, your current catalog stays in place. Reloading the status alone does not refresh tools, and an expired token still requires connecting again.

Why a saved catalog exists

Connections that already exist keep their saved catalog until an admin clicks **Refresh tools**. Meta's server can add tools or change schemas at any time. Sume intersects live discovery with 52 exact reviewed reads, so a new upstream tool never appears for your agents unless it was reviewed and allowed.

What Refresh does and does not do

• Uses the same grant again; no new consent screen
• Replaces the catalog atomically, and only after complete discovery
• Keeps the current catalog if discovery fails
• Adds no scopes
• Does not fix an expired token; connect again for that

A real example from the review

The reviewed-catalog doc records a dest refresh on 2026-09-09 that safely rejected a schema change and kept the old catalog. A second complete official inventory showed one input-schema difference: ads_get_ad_videos added an optional title, described as a case-insensitive substring filter. Policy version 2026-09-09.2 then explicitly accepted both observed video schemas. The policy accepts no other drift, mutation selector or unknown tool.

What this means for your agents

Calls validate against the exact saved variant. The validator rejects title when the stored definition does not advertise it. So if you click Refresh and an agent starts to use a new filter, it is because a reviewed schema variant was accepted, not because Meta changed something silently.

If a Meta read tool your agent expects is missing, ask whether it is on the reviewed list first. Tools like ads_update_entity are excluded on purpose and Refresh will not bring them back.

When to press it

Press Refresh after Sume announces a policy update for Meta Ads, or when an agent reports that a reviewed read tool is absent. Do not press it as a way to fix a token problem. For the token case, reconnect from the Integrations page.

A safe habit

Keep Refresh as a deliberate step. Before you press it, note which Meta read tools your agents rely on. After it, run one agent turn that uses each, so you notice a missing tool immediately instead of in the middle of a report.

Because the replacement is atomic and happens only after complete discovery, the worst case of a failed refresh is that nothing changes. That makes it cheap to retry later.