Kakao Keyword Ads MCP

Overview Schema Source Related Servers Discussions Admin

get_token_info

Read-only

Retrieve the owner and accessible ad accounts for a business token. Use this to verify which ad accounts the token can access.

Instructions

비즈니스 토큰의 소유자(token_user_id)와 접근 가능 광고계정 조회 (GET kapi.kakao.com/v1/business/tokeninfo). biz_agreements[].ad_account_ids가 접근 가능 계정('*'=전체).

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": "get_token_info"
  }
}

Input Schema

Name	Required	Description	Default
`business_token`	No	비즈니스 토큰 (미지정 시 login 세션 사용). override용

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds specific return fields (token_user_id, ad_account_ids) and explains the '*' meaning, providing useful behavioral context beyond annotations.

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?

Description is concise (two sentences) and includes endpoint and key output details. No redundancy, but could be more structured with bullet points.

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?

With output schema present, description doesn't need full return details. It covers main outputs and optional parameter. Adequate for understanding tool functionality.

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 description coverage is 100%, describing the parameter's default and override role. Description adds minimal extra meaning beyond schema, so baseline 3 is appropriate.

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?

Description clearly identifies the tool's purpose: querying business token owner and accessible ad accounts. It specifies the resource (token info) and the verb (query). No sibling tool duplicates this purpose.

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?

No explicit when-to-use or alternatives mentioned. Context implies usage due to unique purpose among siblings, but lacks direct guidance.

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