Skip to main content
Glama
Sign In
tiktok-ads-mcp

tiktok-ads-mcp

by ysntony
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_ads_tool

Retrieve ads for a specific advertiser from TikTok Ads, with optional filtering by ad group and custom criteria.

Instructions

Get ads for a specific advertiser with optional filtering

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": {
      "advertiser_id": "<advertiser_id>"
    },
    "name": "get_ads_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
advertiser_idYes
adgroup_idNo
filtersNo
pageNo
page_sizeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral traits. It only states 'Get ads', implying a read operation, but fails to disclose pagination behavior, rate limits, authentication needs, or any side effects. The output schema exists but is not referenced.

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 description is a single, front-loaded sentence with no wasted words. It is concise but at the expense of completeness, which is acceptable for this dimension since conciseness is valued.

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?

Given 5 parameters, 0% schema coverage, no annotations, and an output schema, the description is insufficient. It omits details on pagination, filtering structure, and the optional adgroup_id parameter, leaving the agent with incomplete context for tool usage.

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

Parameters2/5

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

Schema description coverage is 0%, yet the description only vaguely hints at advertiser_id and filters without explaining any of the 5 parameters. It adds no meaningful semantics beyond the schema's own parameter names and types, leaving adgroup_id, page, and page_size unexplained.

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 description clearly states the tool retrieves ads for a specific advertiser with optional filtering. It distinguishes from sibling tools like get_ad_groups_tool and get_campaigns_tool by specifying the resource and the key identifier (advertiser).

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?

The description does not provide any guidance on when to use this tool versus alternatives. It lacks explicit context for appropriate usage or exclusions, despite the presence of sibling tools like get_authorized_ad_accounts_tool and get_reports_tool.

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

Deploy Server

Other Tools