Skip to main content
Glama
Sign In

Variafy

by com.variafy
OverviewDiscussionsAdmin

Pause, resume or change budgets in TikTok Ads

tiktok_ads_update
Destructive

Pauses or switches back on objects and changes budgets in a TikTok ad account, and pauses or resumes this server’s TikTok monitors. Call tiktok_ads_update with {"action":"execute","tool_name":"tiktok_pause_campaign","arguments":{…}}; arguments carry the fields of the operation and "connection" when several ad accounts are connected. Operations:

  • tiktok_pause_campaign: Pause one TikTok campaign: it stops delivering and spending. Free, and it can be switched back on in TikTok Ads Manager. Free pause.

  • tiktok_pause_adgroup: Pause one TikTok ad group: it stops delivering and spending. Free, and it can be switched back on in TikTok Ads Manager. Free pause.

  • tiktok_pause_ad: Pause one TikTok ad: it stops delivering and spending. Free, and it can be switched back on in TikTok Ads Manager. Free pause.

  • tiktok_lower_campaign_budget: Lower the budget of one TikTok campaign. Only lowering: a higher budget is a separate change that increases spend. Only reduces spend, and counts toward the monthly change limit.

  • tiktok_lower_adgroup_budget: Lower the budget of one TikTok ad group. A daily budget changes from the next day; a lifetime budget at once. Only reduces spend, and counts toward the monthly change limit.

  • tiktok_enable_campaign: Switch one paused TikTok campaign back on: it starts delivering and spending again. CAN INCREASE SPEND, and this account allows it from chat: say so before executing.

  • tiktok_enable_adgroup: Switch one paused TikTok ad group back on: it starts delivering and spending again. CAN INCREASE SPEND, and this account allows it from chat: say so before executing.

  • tiktok_enable_ad: Switch one paused TikTok ad back on: it starts delivering and spending again. CAN INCREASE SPEND, and this account allows it from chat: say so before executing.

  • tiktok_raise_campaign_budget: Raise the budget of one TikTok campaign. It increases spend: approved by a signed-in person unless this account allows it from chat. CAN INCREASE SPEND, and this account allows it from chat: say so before executing.

  • tiktok_raise_adgroup_budget: Raise the budget of one TikTok ad group. A daily budget changes from the next day; a lifetime budget at once. CAN INCREASE SPEND, and this account allows it from chat: say so before executing.

  • tiktok_manage_monitor: Pause or resume a TikTok monitor. Changes only this server’s own monitor, nothing in TikTok, and never counts toward the monthly change limit. Every operation takes two calls with the same tool_name and arguments; the first changes nothing in TikTok and returns a preview. If the operation cannot increase spend, the preview includes confirm_token (accepted for 10 minutes): call again with it added to arguments to apply the change. An operation that can increase spend (switching on, a higher budget) runs from chat only if this account allows it — it does: say plainly that spend will grow before you execute one; otherwise its preview has no token, only an approve_url for a signed-in person. Pauses and monitor changes are free; other changes count toward the monthly change limit. Input schemas: get_tool_schema for named operations; tiktok_ads_read {"action":"list_tools"} lists them all.

Input Schema

NameRequiredDescriptionDefault
actionYesAlways "execute".
argumentsYesThe fields of the operation, "connection" when several ad accounts are connected, and on the second call the confirm_token from the first call.
tool_nameYesThe operation name, e.g. tiktok_pause_campaign.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only flag destructive/idempotent hints; the description goes far beyond by disclosing the preview returns no change, confirm_token lifetime (10 minutes), the approve_url path for spend-increasing operations with no token, and the monthly change limit. It also distinguishes free operations (pauses, monitor changes) from limit-consuming ones.

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?

The envelope and safety rules are front-loaded and the operation list is scannable. Some boilerplate repeats verbatim across entries ('Free pause.', 'CAN INCREASE SPEND, and this account allows it from chat: say so before executing'), which bloats the text without adding per-operation information.

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?

For a mutation tool with no output schema, the description covers everything an agent needs: what each operation does, the two-step confirmation, token expiry, the human-approval fallback, and cost/limit consequences. Nothing material about correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds the meaning of the confirm_token round-trip and the "connection" field's purpose (multiple ad accounts). It also supplies the full operation vocabulary for tool_name, which the schema only exemplifies with one 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?

The opening sentence gives specific verbs (pause, switch back on, change budgets) and the resource (TikTok ad objects, plus this server's monitors), then enumerates every operation by name. It is clearly demarcated from siblings tiktok_ads_create/delete/read, which cover different mutation classes.

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?

It states explicitly when to use it (per-operation breakdown), how to invoke it (the {"action":"execute","tool_name":...,"arguments":{...}} envelope), and the alternative reads for discovery (get_tool_schema, tiktok_ads_read list_tools). The two-call preview-then-confirm protocol is spelled out rather than implied.

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

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