Skip to main content
Glama
Sign In

TikTok Ads MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

TikTok Ads Execute Action

execute_action
Destructive

Execute TikTok Ads action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, account_id AND available_actions

  2. request='actions_details' with actions=['report/integrated/get/'] - Get detailed body structure

Common actions: report/integrated/get/ (performance), ad/get/, campaign/get/, adgroup/get/, advertiser/info/.

Follow the schema from step 2 exactly.

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": {
      "body": "<body>"
    },
    "name": "execute_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds crucial behavioral context beyond annotations: a mandatory multi-step prerequisite chain and the instruction to derive the request body from a prior query_contexts call. It does not elaborate on side effects, failure behavior, or permissions, but with annotations carrying the risk signal this is a solid contribution.

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-loaded with the tool's role and the REQUIRED workflow, using a numbered list that an agent can follow directly. Every sentence serves a purpose (prerequisites, common actions, schema source). The nested parenthetical in '(Step 3 (FINAL) of workflow)' is slightly awkward but does not impede comprehension.

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

Completeness4/5

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

For a high-risk, open-world passthrough tool with a nested open object parameter, the description supplies the prerequisite workflow, common action examples, and the authoritative source for the body schema. Output schema exists, so return values need not be explained. Missing only secondary details such as error behavior or rate-limit handling.

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 description coverage is 0% and the single 'body' parameter is an opaque open object, so the description must compensate. It does so by directing the agent to retrieve the exact body structure from query_contexts request='actions_details' and to follow that schema exactly, which is the correct semantic guidance for a passthrough endpoint. It still gives no inline field-level meaning, which is why it is not a 5.

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?

States a specific verb ('Execute') and a recognizable resource ('TikTok Ads action') and concretizes the abstract 'action' with a list of common endpoints (report/integrated/get/, ad/get/, etc.). It also positions itself relative to the workflow by naming Step 3 (FINAL) and the prerequisite query_contexts calls, so an agent can tell it apart from the sibling query tools.

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?

Explicitly defines the required sequence: call query_contexts with request='accounts' then request='actions_details' before invoking this tool, and says to follow the schema from step 2 exactly. That is strong when-to-use guidance. It does not state when not to use this tool or name alternatives for different action families, which keeps it from a 5.

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

All TikTok Ads MCP by InsightfulPipe 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