Skip to main content
Glama
PlatAid

Kakao Keyword Ads MCP

by PlatAid

get_keyword_performance

Read-only

Retrieve keyword-level performance reports for Kakao Keyword Ads campaigns. Specify campaign ID and optionally ad group ID to analyze metrics like impressions, clicks, and conversions.

Instructions

키워드별 성과 리포트 (GET /keywords/report). campaignId 필수, adGroupId 선택. 검색광고 분석의 핵심.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNo종료일 yyyyMMdd
startNo시작일 yyyyMMdd
time_unitNo기간 단위(선택): DAY 등. 미지정 시 기간 합계
adgroup_idNo특정 광고그룹 한정 (선택)
campaign_idNo캠페인 ID (이 리포트는 필수)
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 endpoint info, no additional behavioral context (e.g., data freshness, metrics returned, pagination).

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?

Very short two-sentence description, concise and to the point, but lacks sufficient detail for full understanding.

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 9 parameters, output schema exists, and numerous sibling tools, the description is too minimal. Missing context on report contents, metrics, time unit behavior, and usage compared to alternatives.

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% with descriptions. Tool description reiterates campaignId required and adGroupId optional, but adds no new meaning beyond 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?

Clearly states it's a keyword performance report, provides endpoint and mandatory parameter. However, does not differentiate from sibling performance reports like get_campaign_performance or get_performance_report.

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?

Mentions campaignId is required and adGroupId optional, but no explicit guidance on when to use this tool versus other performance report tools among siblings.

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