Skip to main content
Glama

Search Papers by Author

search_papers_by_author

Find academic papers by a specific author. Search results can be sorted by publication year or citation count, with pagination support for research.

Instructions

Search papers published by a specific author

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authorYesAuthor 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

  • MCP tool handler that executes the search_papers_by_author logic by calling AminerClient.searchByAuthor, formatting results, and returning as text content or error.
      async ({ author, page, size, order }) => {
        try {
          const result = await aminerClient.searchByAuthor(author, 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
          };
        }
      }
    );
  • Input schema using Zod for validating tool parameters: author (required string), page, size, order.
    inputSchema: {
      author: z.string().describe("Author 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)")
    }
  • src/index.ts:113-149 (registration)
    Registration of the search_papers_by_author tool on the MCP server, including name, metadata, schema, and handler reference.
    server.registerTool(
      "search_papers_by_author",
      {
        title: "Search Papers by Author",
        description: "Search papers published by a specific author",
        inputSchema: {
          author: z.string().describe("Author 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 ({ author, page, size, order }) => {
        try {
          const result = await aminerClient.searchByAuthor(author, 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
          };
        }
      }
    );
  • AminerClient method searchByAuthor that wraps searchPapers with the author parameter.
    /**
     * Search papers by author
     */
    async searchByAuthor(author: string, page = 0, size = 10, order?: 'year' | 'n_citation'): Promise<SearchResult> {
      return this.searchPapers({ author, page, size, order });
    }
  • Core searchPapers helper in AminerClient performing the actual API call to search papers by author (or other params) via HTTP GET with auth.
    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. The description only states the basic action without mentioning pagination behavior, rate limits, authentication needs, error handling, or what the search returns (e.g., paper details). For a search tool with no annotation coverage, this is a significant gap.

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 with zero waste. It's appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

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 complexity of a search tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits, usage context, and what to expect in results, making it inadequate for an agent to fully understand how to invoke and interpret this tool.

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 schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description doesn't add any meaning beyond what the schema provides, such as explaining how author matching works or default behaviors. Baseline 3 is appropriate when the schema does the heavy lifting.

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 as 'Search papers published by a specific author,' which is a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from its siblings (search_papers_advanced, search_papers_by_keyword, search_papers_by_venue), though the name implies differentiation by author versus keyword or venue.

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, prerequisites, or specific contexts where this search method is preferred over others like keyword or venue-based searches.

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