Skip to main content
Glama

ADS Beast

tiktok_ads_account_setup

Read-only

Pixels, identities and account details of a client's TikTok ad account.

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": {
      "client_id": "<client_id>"
    },
    "name": "tiktok_ads_account_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing further — no indication of what the call returns (pixel list? identity list? account metadata?), whether it hits an external API, or how the three listed resource categories are combined. No contradiction with annotations, but no value added either.

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

Conciseness3/5

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

Extremely short and front-loaded, with no wasted words — but the brevity comes from under-specification rather than disciplined editing. It reads as a label for a data category, not a usable tool statement.

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

Completeness2/5

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

With no output schema and no verb, an agent cannot tell whether this returns pixel/identity/account data, whether it creates or only reads setup state, or how the three listed categories relate. For a tool whose name promises "setup," this is a significant gap that the description does nothing to close.

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?

One required parameter (client_id) with 0% schema description coverage. The phrase "a client's TikTok ad account" is the only signal tying client_id to a client scope, which is a marginal but real clarification; it still does not say the expected type, how the client maps to an ad account, or what happens for an invalid/missing client.

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

Purpose3/5

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

The description is a noun phrase ("Pixels, identities and account details of a client's TikTok ad account") with no verb, so it enumerates the resource scope but never states the action — retrieve, configure, or provision. The name and platform-reference distinguish it from linkedin/meta/microsoft_ads_account_setup siblings, but the description itself does not.

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

Usage Guidelines2/5

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

No statement of when to call this, no prerequisites, and no mention of the parallel *_ads_account_setup siblings or any alternative. The agent must infer usage entirely from the name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.