Skip to main content
Glama

google_scholar_author

Retrieve comprehensive author profiles from Google Scholar: name, affiliation, email, publication list with citation counts, and co-author details via list_colleagues mode.

Instructions

Retrieves comprehensive author information from a Google Scholar profile: name, affiliation, email, and publication/citation history. The same endpoint also exposes a co-author list mode via view_op=list_colleagues. [Credits: Not explicitly stated on this documentation page.] Notes: IMPORTANT AMBIGUITY: this endpoint's URL (/google_scholar/author) is identical to the one documented separately as 'google_scholar_author_citation'. The two documentation pages describe the same physical endpoint used in two modes: (1) default/no view_op -> full author profile + article list (this tool), and (2) view_op=view_citation + citation_id -> single citation detail with h-index/i10-index/citation graph (see google_scholar_author_citation). Consider merging these into one MCP tool with an optional view_op/citation_id argument, or keep separate tools that both call the same endpoint with different required params. Returns: { author: { name, affiliations, email }, articles: [ { title, citation_id, authors, publication, cited_by: { value }, year } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort articles: title (by article title) or pubdate (by publication date).
resultsNoNumber of results (articles) per page.
view_opNoAccess a specific section of the author page: view_citation (requires citation_id, returns a single citation's detail) or list_colleagues (returns all co-authors).
languageNoLanguage of the results, e.g. en, es, fr, de. See Google Language Page. (default: en)
author_idYesAuthor ID of the person to get data for (obtainable from google_scholar_profiles results as profiles[].author_id).
citation_idNoID of an individual article's citation; required only when view_op=view_citation. Obtainable from this endpoint's articles[].citation_id.
Behavior4/5

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

With no annotations provided, the description carries full burden. It explains the two modes (default profile vs list_colleagues) and the ambiguity with the sibling endpoint, and provides a return structure. It could mention authentication or rate limits but is still clear.

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 structured well with a clear main purpose followed by notes. The ambiguity note is lengthy but important. Front-loaded with core functionality. Could be slightly more concise.

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 the absence of an output schema, the description provides a complete return structure and covers all parameters and modes. It addresses the sibling tool relationship and potential confusion, making it fully informative for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter is described. The description adds context beyond schema by explaining the behavioral differences of view_op values and the relationship between author_id and citation_id. However, it repeats some schema info.

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 clearly states it retrieves comprehensive author information (name, affiliation, email, publication/citation history) and also exposes a co-author list mode. It explicitly distinguishes from the sibling tool 'google_scholar_author_citation' by explaining the ambiguity and the two modes of the same endpoint.

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?

The description provides explicit guidance on when to use this tool versus the citation tool, including the note about potential merging. It also mentions how to obtain the author_id from the profiles tool and prerequisites for using citation_id.

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/alessandrobenigni/ScrapingDog-MCP'

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