Skip to main content
Glama

AdsAgent — TikTok Ads MCP

by md.adsagent
OverviewDiscussionsAdmin

Read and reconcile an operation receipt

operations_get
Destructive

Recover tnapi_ native API receipts independently of Agent Method feature gates. Read or safely recover a bounded TikTok write receipt by the canonical operation_ref returned by create or delivery confirmation. The legacy mutation_ref argument remains accepted for older delivery-status clients; pass exactly one reference. Recovery uses TikTok getters on the exact original tenant, advertiser, and authorization route. It never replays a write or name-matches an uncertain result.

Recovery can update the stored operation receipt after provider readback; it never replays the advertising write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mutation_refNo
operation_refNo
connection_contextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / mutation_ref / anyOf
      Previous value: -[
-  {
-    "maxLength": 160,
-    "minLength": 12,
-    "pattern": "^(?:(?:tmut_|tcreate[_-])[A-Za-z0-9_-]+|tnapi_[a-f0-9]{64})$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 160,
+    "minLength": 12,
+    "pattern": "^(?:(?:tmut_|tcreate[_-]|batch_)[A-Za-z0-9_-]+|tnapi_[a-f0-9]{64})$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / operation_ref / anyOf
      Previous value: -[
-  {
-    "maxLength": 160,
-    "minLength": 12,
-    "pattern": "^(?:(?:tmut_|tcreate[_-])[A-Za-z0-9_-]+|tnapi_[a-f0-9]{64})$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 160,
+    "minLength": 12,
+    "pattern": "^(?:(?:tmut_|tcreate[_-]|batch_)[A-Za-z0-9_-]+|tnapi_[a-f0-9]{64})$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / connection_context
      Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / mutation_ref / anyOf
      Previous value: -[
-  {
-    "maxLength": 160,
-    "minLength": 12,
-    "pattern": "^(?:tmut_|tcreate[_-])[A-Za-z0-9_-]+$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 160,
+    "minLength": 12,
+    "pattern": "^(?:(?:tmut_|tcreate[_-])[A-Za-z0-9_-]+|tnapi_[a-f0-9]{64})$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / operation_ref / anyOf
      Previous value: -[
-  {
-    "maxLength": 160,
-    "minLength": 12,
-    "pattern": "^(?:tmut_|tcreate[_-])[A-Za-z0-9_-]+$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 160,
+    "minLength": 12,
+    "pattern": "^(?:(?:tmut_|tcreate[_-])[A-Za-z0-9_-]+|tnapi_[a-f0-9]{64})$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations carry destructiveHint=true and readOnlyHint=false, and the description explains precisely why: recovery 'can update the stored operation receipt after provider readback' while it 'never replays the advertising write.' This reconciles the destructive flag with the get-sounding name and adds real behavioral context beyond the annotations, though it omits error/partial-recovery behavior.

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 core action and dense with useful detail. The closing sentence ('it never replays the advertising write') restates the earlier 'It never replays a write', a minor redundancy, but overall there is little waste.

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?

No output schema exists, so the description carries the burden, and it covers purpose, the two reference forms, the safety/side-effect model, and the readback route. It does not describe the receipt content returned or failure modes, leaving a modest gap for a reconcile operation.

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?

With 0% schema description coverage, the description must compensate, and it does for the critical ambiguity: operation_ref is the canonical reference returned by create/delivery confirmation, mutation_ref is a legacy argument for older delivery-status clients, and 'pass exactly one reference' resolves the optional-both-nullable schema. Only connection_context is left unexplained.

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 and resource: 'Read or safely recover a bounded TikTok write receipt' by its operation_ref. This is unambiguous about what the tool does, but it never names or contrasts with a sibling tool, so it falls short of the sibling-differentiation bar for 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 Guidelines3/5

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

It gives a usage context ('by the canonical operation_ref returned by create or delivery confirmation') and notes legacy clients should use mutation_ref, which is genuinely implied guidance. However, there is no explicit when-not-to-use and no naming of an alternative receipt/reconciliation tool among the many siblings.

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

All AdsAgent — TikTok Ads MCP 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