Skip to main content
Glama

Search Papers by Venue

search_papers_by_venue

Find academic papers published in specific journals or conferences. Search by venue name, sort by year or citations, and browse results with pagination.

Instructions

Search papers published in a specific venue/journal

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
venueYesVenue/journal name
pageNoPage number, starting from 0
sizeNoNumber of papers per page, maximum 10
orderNoSort order: year (by publication year) or n_citation (by citation count)

Implementation Reference

  • src/index.ts:74-110 (registration)
    Full registration of the MCP tool 'search_papers_by_venue', including input schema (Zod validation) and inline handler function that delegates to AminerClient.
    server.registerTool(
      "search_papers_by_venue",
      {
        title: "Search Papers by Venue",
        description: "Search papers published in a specific venue/journal",
        inputSchema: {
          venue: z.string().describe("Venue/journal name"),
          page: z.number().min(0).default(0).describe("Page number, starting from 0"),
          size: z.number().min(1).max(10).default(10).describe("Number of papers per page, maximum 10"),
          order: z.enum(["year", "n_citation"]).optional().describe("Sort order: year (by publication year) or n_citation (by citation count)")
        }
      },
      async ({ venue, page, size, order }) => {
        try {
          const result = await aminerClient.searchByVenue(venue, page, size, order);
          const formattedResult = aminerClient.formatSearchResults(result);
          
          return {
            content: [{
              type: "text",
              text: JSON.stringify(formattedResult, null, 2)
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: JSON.stringify({
                error: "Search failed",
                message: error instanceof Error ? error.message : 'Unknown error'
              }, null, 2)
            }],
            isError: true
          };
        }
      }
    );
  • The MCP tool handler function: extracts parameters, calls AminerClient.searchByVenue, formats results with formatSearchResults, returns JSON or error.
    async ({ venue, page, size, order }) => {
      try {
        const result = await aminerClient.searchByVenue(venue, page, size, order);
        const formattedResult = aminerClient.formatSearchResults(result);
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify(formattedResult, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              error: "Search failed",
              message: error instanceof Error ? error.message : 'Unknown error'
            }, null, 2)
          }],
          isError: true
        };
      }
    }
  • Zod input schema defining validation for tool parameters: venue (required string), page/size (numbers), order (enum).
    inputSchema: {
      venue: z.string().describe("Venue/journal name"),
      page: z.number().min(0).default(0).describe("Page number, starting from 0"),
      size: z.number().min(1).max(10).default(10).describe("Number of papers per page, maximum 10"),
      order: z.enum(["year", "n_citation"]).optional().describe("Sort order: year (by publication year) or n_citation (by citation count)")
    }
  • AminerClient.searchByVenue method: wrapper that calls the core searchPapers with venue parameter.
    async searchByVenue(venue: string, page = 0, size = 10, order?: 'year' | 'n_citation'): Promise<SearchResult> {
      return this.searchPapers({ venue, page, size, order });
    }
  • Core searchPapers helper: builds query params including venue, makes authenticated GET request to AMiner API, processes response into SearchResult.
    async searchPapers(params: SearchParams): Promise<SearchResult> {
      // Validate required parameters
      if (!params.keyword && !params.venue && !params.author) {
        throw new Error('At least one of keyword, venue, or author must be provided');
      }
    
      if (params.size > 10) {
        throw new Error('Size parameter cannot exceed 10');
      }
    
      // Build query parameters
      const searchParams = new URLSearchParams();
      if (params.keyword) searchParams.append('keyword', params.keyword);
      if (params.venue) searchParams.append('venue', params.venue);
      if (params.author) searchParams.append('author', params.author);
      searchParams.append('page', params.page.toString());
      searchParams.append('size', params.size.toString());
      if (params.order) searchParams.append('order', params.order);
    
      const url = `${this.config.baseUrl}?${searchParams.toString()}`;
    
      try {
        const response = await fetch(url, {
          method: 'GET',
          headers: {
            'Authorization': this.config.apiKey,
            'Content-Type': 'application/json',
          },
        });
    
        if (!response.ok) {
          throw new Error(`HTTP ${response.status}: ${response.statusText}`);
        }
    
        const data = await response.json() as AminerSearchResponse;
    
        // Add detailed response data check
        if (!data) {
          throw new Error('API returned empty response');
        }
    
        if (!data.success) {
          throw new Error(`API Error (${data.code}): ${data.msg}`);
        }
    
        // Check the completeness of the response data
        if (typeof data.total !== 'number') {
          console.warn('API response missing or invalid total field, defaulting to 0');
        }
    
        // Ensure data.data is not null, if it is null, use an empty array
        const papers = data.data || [];
        const total = data.total || 0;
    
        return {
          papers,
          total,
          page: params.page,
          size: params.size,
          hasMore: (params.page + 1) * params.size < total,
        };
      } catch (error) {
        if (error instanceof Error) {
          throw new Error(`Failed to search papers: ${error.message}`);
        }
        throw new Error('Unknown error occurred while searching papers');
      }
    }
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 only states the basic action ('Search papers') without detailing aspects like pagination behavior (implied by 'page' and 'size' parameters but not explained), rate limits, authentication needs, or what the search returns. For a tool with 4 parameters and no annotations, this is a significant gap in transparency.

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 a single, efficient sentence: 'Search papers published in a specific venue/journal'. It is front-loaded with the core purpose, has zero wasted words, and is appropriately sized for the tool's complexity.

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 the tool's complexity (4 parameters, no annotations, no output schema), the description is incomplete. It lacks information on behavioral traits, usage guidelines, and output expectations. While the schema covers parameters well, the description fails to provide sufficient context for effective tool invocation and understanding of results.

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%, meaning all parameters are well-documented in the input schema. The description adds no additional meaning beyond what the schema provides (e.g., it doesn't explain parameter interactions or usage nuances). With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 tool's purpose: 'Search papers published in a specific venue/journal'. It specifies the verb ('Search') and resource ('papers'), and distinguishes the scope by venue/journal. However, it doesn't explicitly differentiate from sibling tools like search_papers_by_author or search_papers_by_keyword, which is why it doesn't reach a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like search_papers_advanced, search_papers_by_author, or search_papers_by_keyword, nor does it specify scenarios where this tool is preferred or excluded. This leaves the agent without context for selection.

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/scipenai/aminer-mcp-server'

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