Kakao Keyword Ads MCP

by PlatAid

Overview Schema Source Related Servers Discussions Admin

Python

Remote

list_creatives

Read-only

Retrieve creatives for a specific business channel using its ID. Requires the biz_channel_id from list_campaigns.

Instructions

소재 목록 (GET /creatives/basic?bizChannelId=). bizChannelId 필수 — 캠페인의 bizChannelId 값을 넘긴다 (소재는 비즈채널 단위).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_creatives"
  }
}

Input Schema

Name	Required	Description
`ad_account_id`	No	대상 광고계정 ID (미지정 시 use_account 세션 사용)
`biz_channel_id`	No	비즈채널 ID (필수). list_campaigns의 bizChannelId 사용
`business_token`	No	비즈니스 토큰 (미지정 시 login 세션 사용). override용

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The description adds the HTTP method (GET) and parameter dependency beyond the readOnlyHint annotation. It also notes that creatives are per biz channel. No contradictions with annotations. The added behavioral context is useful.

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 very concise, consisting of two short phrases. It front-loads the purpose and key parameter. While brief, every part is relevant and it avoids unnecessary repetition.

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?

Given the presence of an output schema, the description does not need to detail return values. It covers the essential aspects: what the tool does and how to use the primary parameter. Missing details like pagination are acceptable for a simple list tool with an output schema.

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?

Although schema coverage is 100%, the description adds value by indicating the parameter's source (list_campaigns) and emphasizing it as 'required'. However, the schema marks the parameter as nullable with default null, creating a minor inconsistency. Overall, it provides additional guidance beyond the schema.

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?

The description clearly states the tool lists creatives, mentions the HTTP endpoint, and specifies the key parameter bizChannelId. While it does not explicitly contrast with sibling 'get_creative', the plural name and context imply a list operation, making the purpose clear.

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?

The description advises to pass the bizChannelId from list_campaigns, providing some usage context. However, it does not explicitly state when to use this tool versus alternatives like get_creative, nor does it mention when not to use it. Guidance is implicit but lacks exclusivity.

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