Skip to main content
Glama
PlatAid

Kakao Keyword Ads MCP

by PlatAid

get_performance_report

Read-only

Retrieve aggregated performance reports for Kakao Keyword Ads by account, campaign, ad group, keyword, or creative level to analyze ad metrics and gain insights.

Instructions

레벨 지정 통합 성과 리포트 (KEYWORD 포함). 인사이트 도출용 1급 툴. AD_GROUP/KEYWORD/CREATIVE 레벨은 campaign_id 필수.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNo종료일 yyyyMMdd
levelYes집계 레벨: AD_ACCOUNT | CAMPAIGN | AD_GROUP | KEYWORD | CREATIVE
startNo시작일 yyyyMMdd
time_unitNo기간 단위(선택): DAY 등. 미지정 시 기간 합계
adgroup_idNo광고그룹 ID (KEYWORD/CREATIVE 선택)
campaign_idNo캠페인 ID (AD_GROUP/KEYWORD/CREATIVE 레벨 필수)
date_presetNoTODAY/YESTERDAY/LAST_7DAY 등 (기간과 택일)
ad_account_idNo대상 광고계정 ID (미지정 시 use_account 세션 사용)
metrics_groupNo지표 그룹(쉼표구분 복수 가능): BASIC/ADDITION/PIXEL_SDK_CONVERSIONBASIC
business_tokenNo비즈니스 토큰 (미지정 시 login 세션 사용). override용

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations already declare readOnlyHint=true. Description adds only a vague 'tier-1 tool for insights' without further behavioral details (e.g., default date range, pagination, or error conditions).

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 (two sentences) and front-loads the primary purpose. No wasted words, though a bit more structure could help readability.

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

Completeness3/5

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

Given the tool's complexity (10 params, output schema exists), the description covers the essential behavior but misses context like how it differs from sibling performance tools. Adequate but not thorough.

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?

Schema coverage is 100%, so the description does not need to add parameter details. The only added note about campaign_id requirement is already present in the schema description. Baseline score of 3 is appropriate.

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 states the tool returns a 'level-specified integrated performance report' and highlights its importance for insights. It distinguishes from sibling tools by being flexible across levels, but does not fully clarify when to use this versus specific get_*_performance tools.

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 explicit guidance on when to use this tool versus siblings like get_campaign_performance. Only mentions a parameter requirement (campaign_id for certain levels), which is not a usage guideline.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PlatAid/kakao-keywordad-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server