Skip to main content
Glama

한국일보 뉴스 (Hankookilbo)

많이 본 인기 뉴스 (분야/전체)

list_popular_news
Read-only

'인기 뉴스', '많이 본 기사', '오늘 가장 많이 본 뉴스', '핫한/화제의 기사', '지금 뜨는 뉴스'처럼 조회수 기준 인기(많이 본) 순위는 기본적으로 이 도구입니다. section_cd='all'이면 사이트 전체, 분야 코드를 넣으면 해당 분야 인기 기사입니다(예: section_cd='politics' = 정치 인기 기사). 이것이 조회수 기반 인기 순위이며, 편집부 추천(list_recommended_articles)과 구분됩니다. 사용자가 콕 집어 '꼼꼼히 본 뉴스'를 원할 때만 list_most_read_news 를 쓰세요. 전체 조회 시 exclude_section_cd 로 특정 분야를 제외할 수 있습니다.

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_popular_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_sizeNo가져올 기사 수(1~최대치로 클램프).
section_cdNo섹션 코드 슬러그(소문자). 'all'=사이트 전체. list_sections 참고.all
exclude_section_cdNosection_cd='all' 전체 조회 시 제외할 섹션 코드 슬러그.

Output Schema

NameRequiredDescriptionDefault
pageNo페이징 메타데이터(있을 때).
itemsNo기사 카드 목록.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this as a read-only, non-destructive, open-world tool. The description adds meaningful behavioral context by explaining that results are ranked by view count and by contrasting this with editorial recommendation behavior, though it does not discuss freshness windows or ranking details beyond that.

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 front-loaded with the core routing rule and alternative tools, and every part is relevant. It is slightly repetitive in restating that this is the view-count-based popularity ranking, but the redundancy reinforces a subtle sibling distinction rather than derailing the agent.

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

Completeness5/5

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

Given that annotations cover safety behavior, the input schema fully documents parameters, and an output schema exists, the description supplies the remaining critical context: ranking basis, section vs whole-site scope, and sibling routing. Nothing essential for correct invocation is missing.

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%, so the schema already documents page_size, section_cd, and exclude_section_cd thoroughly. The description adds a useful example for section_cd='politics' and clarifies whole-site exclusion behavior, but it mostly recaps what the schema already provides and does not address page_size.

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 states a specific resource and ranking basis: view-count-based popular news, with optional section scoping. It explicitly distinguishes this tool from list_recommended_articles and list_most_read_news, so an agent can route popularity queries without inspecting sibling schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit default-use guidance for popularity queries and names the alternatives by condition: use list_recommended_articles for editorial recommendations and list_most_read_news only when the user specifically asks for '꼼꼼히 본 뉴스'. This is clear when-to-use and when-not-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.