Skip to main content
Glama

Adeli

by com.tryadeli.app
OverviewDiscussionsAdmin

Activate or pause an ad

ads_set_status
Destructive

Set a campaign, ad set (TikTok ad group) or ad to ACTIVE or PAUSED. TikTok needs level. ACTIVE starts spending real money on the ad account: never activate without the user's explicit confirmation of the budget and dates.

Input Schema

NameRequiredDescriptionDefault
levelNo
statusYes
objectIdYes
platformNometa_ads or tiktok_ads. Needed only when the profile has both ad networks and no accountId is given.
accountIdNoThe Facebook accountId from list_accounts. Without it, pass profileId to use that profile's Facebook connection.
profileIdNoA profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree.
adAccountIdYes
campaignRecordIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / adAccountId / pattern
      Previous value: -"^act_\\d+$"New value: +"^(act_)?\\d+$"
    • addedInput schema / properties / level
      Added value: +{
+  "enum": [
+    "campaign",
+    "ad_group",
+    "ad"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / platform
      Added value: +{
+  "description": "meta_ads or tiktok_ads. Needed only when the profile has both ad networks and no accountId is given.",
+  "enum": [
+    "meta_ads",
+    "tiktok_ads"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / accountId / description
      Previous value: -"The Facebook accountId from list_accounts. Defaults to the profile's Facebook connection."New value: +"The Facebook accountId from list_accounts. Without it, pass profileId to use that profile's Facebook connection."
    • changedInput schema / properties / profileId / description
      Previous value: -"Defaults to the profile your API key is bound to."New value: +"A profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds the critical business consequence the annotations cannot convey: ACTIVE starts spending real money on the ad account and requires explicit user confirmation of budget and dates. It also discloses a per-platform behavioral requirement (TikTok needs level). It does not say whether the change is reversible or what the response looks like.

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

Conciseness5/5

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

Two sentences, no filler. The action and scope come first, then the spend-risk warning and the TikTok parameter caveat. Every clause carries operational value.

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

Completeness3/5

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

For an 8-parameter, destructive, no-output-schema tool, the description covers the highest-stakes behavior well but leaves the identifier parameters (objectId, adAccountId, campaignRecordId) unexplained and does not mention that accountId/profileId can be derived per the schema descriptions. Adequate but with clear gaps in how to identify the target object.

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 description coverage is only 38% across 8 parameters, so the description must compensate, and it partly does: it tells the agent that `level` is required for TikTok and that `status` toggles real spend. But objectId, adAccountId, and campaignRecordId receive no explanation in either the description or the schema, leaving the core identifier wiring undocumented.

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

Purpose4/5

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

The first sentence states a specific verb (set to ACTIVE/PAUSED) and enumerates the exact resources it applies to (campaign, ad set / TikTok ad group, ad), which cleanly separates it from sibling updaters like ads_update_ad_group or ads_delete_campaign. It stops short of explicitly naming a sibling as the alternative path, so it isn't a 5.

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

Usage Guidelines4/5

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

It gives a clear when-to-use context (pausing/activating at any of three levels, with the TikTok level requirement called out) and an explicit when-not/guardrail: never activate without the user's explicit confirmation of budget and dates. No named alternatives, but the risky-path guidance is unusually concrete.

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

All Adeli 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