Skip to main content
Glama
TeeDDub

Aladin Book Search MCP Server

by TeeDDub

편집자 추천 리스트

get_editor_choice

Retrieve curated editor-recommended book lists from Aladin’s API. Filter results by category, set max results, and define search start points for precise selections.

Instructions

알라딘 편집자 추천 리스트를 조회합니다. 카테고리별로 검색할 수 있습니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryIdNo카테고리 ID (CID) - 특정 카테고리로 검색을 제한할 때 사용
maxResultsNo최대 결과 개수
startNo검색 시작 번호

Implementation Reference

  • Handler function that implements the 'get_editor_choice' tool. It calls the Aladin API with QueryType 'ItemEditorChoice' to fetch editor-recommended books, processes the results into a standardized BookSearchResult format, and returns formatted text output.
    async ({ maxResults, start, categoryId }) => {
      try {
        const params: any = {
          QueryType: 'ItemEditorChoice',
          MaxResults: maxResults,
          start: start,
          SearchTarget: 'Book',
          Cover: 'Big'
        };
    
        if (categoryId) {
          params.CategoryId = categoryId;
        }
    
        const result = await callAladinApi('ItemList.aspx', params);
        
        const books: BookSearchResult[] = result.item?.map((item: any) => ({
          title: item.title || '',
          author: item.author || '',
          publisher: item.publisher || '',
          pubDate: item.pubDate || '',
          isbn: item.isbn || '',
          isbn13: item.isbn13 || '',
          cover: item.cover || '',
          categoryName: item.categoryName || '',
          description: item.description || '',
          priceStandard: item.priceStandard || 0,
          priceSales: item.priceSales || 0,
          link: item.link || '',
          pages: item.subInfo?.itemPage || undefined,
          pricePerPage: (item.priceStandard > 0 && item.subInfo?.itemPage > 0) 
            ? parseFloat((item.priceStandard / item.subInfo.itemPage).toFixed(2)) 
            : undefined
        })) || [];
    
        const categoryText = categoryId ? ` (카테고리: ${categoryId})` : '';
        
        return {
          content: [{
            type: 'text',
            text: `👨‍💼 편집자 추천 리스트${categoryText}\n\n검색된 도서 수: ${books.length}권\n\n${JSON.stringify(books, null, 2)}`
          }]
        };
      } catch (error) {
        logger.error(`편집자 추천 리스트 조회 중 오류 발생: ${error}`);
        return {
          content: [{
            type: 'text',
            text: `편집자 추천 리스트 조회 중 오류가 발생했습니다: ${error instanceof Error ? error.message : String(error)}`
          }],
          isError: true
        };
      }
    }
  • Input schema definition for the 'get_editor_choice' tool using Zod, specifying parameters for maxResults, start, and optional categoryId.
      title: '편집자 추천 리스트',
      description: '알라딘 편집자 추천 리스트를 조회합니다. 카테고리별로 검색할 수 있습니다.',
      inputSchema: {
        maxResults: z.number().min(1).max(100).default(10).describe('최대 결과 개수'),
        start: z.number().min(1).default(1).describe('검색 시작 번호'),
        categoryId: z.string().optional().describe('카테고리 ID (CID) - 특정 카테고리로 검색을 제한할 때 사용')
      }
    },
  • src/index.ts:537-601 (registration)
    Registration of the 'get_editor_choice' tool using server.registerTool, including name, schema/spec, and handler function.
      'get_editor_choice',
      {
        title: '편집자 추천 리스트',
        description: '알라딘 편집자 추천 리스트를 조회합니다. 카테고리별로 검색할 수 있습니다.',
        inputSchema: {
          maxResults: z.number().min(1).max(100).default(10).describe('최대 결과 개수'),
          start: z.number().min(1).default(1).describe('검색 시작 번호'),
          categoryId: z.string().optional().describe('카테고리 ID (CID) - 특정 카테고리로 검색을 제한할 때 사용')
        }
      },
      async ({ maxResults, start, categoryId }) => {
        try {
          const params: any = {
            QueryType: 'ItemEditorChoice',
            MaxResults: maxResults,
            start: start,
            SearchTarget: 'Book',
            Cover: 'Big'
          };
    
          if (categoryId) {
            params.CategoryId = categoryId;
          }
    
          const result = await callAladinApi('ItemList.aspx', params);
          
          const books: BookSearchResult[] = result.item?.map((item: any) => ({
            title: item.title || '',
            author: item.author || '',
            publisher: item.publisher || '',
            pubDate: item.pubDate || '',
            isbn: item.isbn || '',
            isbn13: item.isbn13 || '',
            cover: item.cover || '',
            categoryName: item.categoryName || '',
            description: item.description || '',
            priceStandard: item.priceStandard || 0,
            priceSales: item.priceSales || 0,
            link: item.link || '',
            pages: item.subInfo?.itemPage || undefined,
            pricePerPage: (item.priceStandard > 0 && item.subInfo?.itemPage > 0) 
              ? parseFloat((item.priceStandard / item.subInfo.itemPage).toFixed(2)) 
              : undefined
          })) || [];
    
          const categoryText = categoryId ? ` (카테고리: ${categoryId})` : '';
          
          return {
            content: [{
              type: 'text',
              text: `👨‍💼 편집자 추천 리스트${categoryText}\n\n검색된 도서 수: ${books.length}권\n\n${JSON.stringify(books, null, 2)}`
            }]
          };
        } catch (error) {
          logger.error(`편집자 추천 리스트 조회 중 오류 발생: ${error}`);
          return {
            content: [{
              type: 'text',
              text: `편집자 추천 리스트 조회 중 오류가 발생했습니다: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes a read operation ('조회합니다'), which is clear, but lacks details about rate limits, authentication requirements, pagination behavior (beyond the 'start' parameter), or what the return format looks like. For a tool with 3 parameters and no annotations, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences with zero waste. The first sentence states the core purpose, and the second adds key functionality (category filtering). It's appropriately sized and front-loaded, making it easy to parse quickly.

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 no annotations and no output schema, the description is adequate but incomplete. It covers the basic purpose and hints at filtering, but doesn't address behavioral aspects like response format, error handling, or usage constraints. For a read-only tool with 3 parameters, it meets minimum viability but lacks depth.

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?

The description mentions category-based search, which aligns with the 'categoryId' parameter. However, with 100% schema description coverage, the input schema already fully documents all three parameters ('categoryId', 'maxResults', 'start') with clear descriptions and defaults. The description adds minimal value beyond what's in the schema, meeting the baseline for high coverage.

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 verb ('조회합니다' - retrieve/query) and resource ('알라딘 편집자 추천 리스트' - Aladdin editor recommendation list), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'get_bestsellers' or 'get_new_books' beyond mentioning it's specifically for editor recommendations.

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 mentions '카테고리별로 검색할 수 있습니다' (can search by category), which implies usage context for filtering. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'get_bestsellers' or 'search_books', nor does it mention any exclusions or prerequisites for use.

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

Related 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/TeeDDub/mcp-aladin-books-server'

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