Skip to main content
Glama
Sign In

Apogee: Bulk Ad Launcher for Meta, TikTok & Snapchat

by ad.apogee
OverviewDiscussionsAdmin

Refresh Meta ad comments

trigger_comment_sync

Refresh the Meta ad comments Apogee holds. Trigger a Comment Analysis sync to fetch fresh ad comments from Meta. Use this when fetch_ad_comments returns stale data (sync_status="stale_suggest_refresh") or no data at all. The sync runs asynchronously (takes 1-5 minutes depending on the number of ads). After triggering, tell the user the sync has started and that fresh comments will be available shortly — or in a follow-up conversation. Choose period_days: 30 (default, faster) or 90 (deeper, slower). The synced comments are shared with the Comment Analysis page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ad_account_id": "<ad_account_id>"
    },
    "name": "trigger_comment_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
period_daysNoHow far back to sync comments. 30 days (faster, default) or 90 days (deeper).
ad_account_idYesMeta ad account id (act_…), from list_ad_accounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare the coarse safety profile (not read-only, open world, non-idempotent, non-destructive). The description adds the operationally critical facts: the sync is asynchronous, takes 1-5 minutes depending on ad count, results appear later rather than in the response, and the data is shared with the Comment Analysis page.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads what the tool does, then the trigger condition, then the async timing, then the parameter choice. Each sentence contributes, though the user-messaging instruction is slightly verbose relative to the rest.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description covers what an agent needs: the call is fire-and-forget, results arrive in 1-5 minutes, and the agent should tell the user rather than wait. Nothing essential about invocation or follow-up is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents both ad_account_id and the 30/90 period_days enum with the same faster/deeper framing. The description's '30 (default, faster) or 90 (deeper, slower)' largely restates the schema, so it adds only marginal value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Refresh the Meta ad comments Apogee holds' and 'Trigger a Comment Analysis sync to fetch fresh ad comments from Meta'. It is clearly distinguishable from read-only siblings like fetch_ad_comments, which it explicitly references.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition ('when fetch_ad_comments returns stale data (sync_status="stale_suggest_refresh") or no data at all') and names the alternative by name. No ambiguity about when to reach for this versus reading comments directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Apogee: Bulk Ad Launcher for Meta, TikTok & Snapchat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources