Skip to main content
Glama
TeeDDub

Aladin Book Search MCP Server

by TeeDDub

주목할 만한 신간 리스트

get_special_new_books

Retrieve notable new book releases from Aladin, filtered by category, to stay updated on trending and specialized literature.

Instructions

알라딘 주목할 만한 신간 리스트를 조회합니다. 카테고리별로 검색할 수 있습니다.

Input Schema

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

Implementation Reference

  • The main handler function for the 'get_special_new_books' tool. It constructs parameters for the Aladin API with QueryType 'ItemNewSpecial', calls the API via callAladinApi, maps the response items to BookSearchResult objects, and returns a formatted text response or error.
    async ({ maxResults, start, categoryId }) => {
      try {
        const params: any = {
          QueryType: 'ItemNewSpecial',
          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
        };
      }
    }
  • src/index.ts:467-533 (registration)
    The server.registerTool call that registers the 'get_special_new_books' tool, including its title, description, input schema, and handler function.
    // 주목할 만한 신간 리스트 도구 등록
    server.registerTool(
      'get_special_new_books',
      {
        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: 'ItemNewSpecial',
            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
          };
        }
      }
    );
  • Zod input schema defining parameters for the tool: maxResults, start, and optional categoryId.
    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) - 특정 카테고리로 검색을 제한할 때 사용')
    }
  • TypeScript interface BookSearchResult used to type the processed book data in the handler's result mapping.
    interface BookSearchResult {
      title: string;
      author: string;
      publisher: string;
      pubDate: string;
      isbn: string;
      isbn13: string;
      cover: string;
      categoryName: string;
      description: string;
      priceStandard: number;
      priceSales: number;
      link: string;
      pages?: number; // 페이지 수 추가
      pricePerPage?: number; // 쪽단가 추가
    }
  • Helper function callAladinApi that makes HTTP requests to the Aladin API endpoints, used by the handler to fetch 'ItemList.aspx' with the specified parameters.
    async function callAladinApi(endpoint: string, params: Record<string, any>): Promise<any> {
      if (!ALADIN_TTB_KEY || ALADIN_TTB_KEY.length === 0) {
        throw new Error('알라딘 API 키가 설정되지 않았습니다. ALADIN_TTB_KEY 환경변수를 올바르게 설정해주세요.');
      }
    
      const baseParams = {
        ttbkey: ALADIN_TTB_KEY,
        output: 'js',
        version: '20131101'
      };
    
      const finalParams = { ...baseParams, ...params };
      const url = `${ALADIN_BASE_URL}/${endpoint}`;
    
      try {
        const response = await axios.get(url, { params: finalParams });
        return response.data;
      } catch (error) {
        logger.error(`알라딘 API 호출 오류: ${error}`);
        throw error;
      }
    }
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. It mentions retrieval and category filtering but fails to disclose critical behavioral traits such as whether this is a read-only operation, rate limits, authentication needs, pagination behavior (implied by 'start' and 'maxResults' but not explained), or what the return format looks like (no output schema).

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 concise with two sentences that are front-loaded and to the point. However, it could be slightly more structured by explicitly separating purpose from usage context.

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 no annotations and no output schema, the description is incomplete. It covers the basic purpose and hints at category usage but lacks details on behavioral aspects, return values, error handling, or how it differs from sibling tools, leaving significant gaps for an AI agent.

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 fully documents parameters like 'categoryId', 'maxResults', and 'start'. The description adds marginal value by mentioning category-based search, aligning with 'categoryId', but does not provide additional semantics beyond what the schema already covers.

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) and resource '알라딘 주목할 만한 신간 리스트' (Aladin notable new books list), making the purpose explicit. It distinguishes from siblings like 'get_new_books' by specifying '주목할 만한' (notable/worthy of attention), though this distinction could be more precise.

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 implies usage for retrieving notable new books by category, but does not explicitly state when to use this tool versus alternatives like 'get_new_books' or 'get_bestsellers'. It mentions category-based search but lacks guidance on exclusions or prerequisites.

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