google-scholar-mcp

get_author_profile

Retrieve a Google Scholar author profile with publications, citation metrics (h-index, i10-index), and coauthor list.

Instructions

Get detailed information about a specific Google Scholar author profile, including publications, citation metrics (h-index, i10-index), and coauthors.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scholarId": "<scholarId>"
    },
    "name": "get_author_profile"
  }
}

Input Schema

Name	Required	Description	Default
`scholarId`	Yes	Google Scholar author ID (e.g., "JicYPdAAAAAJ")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 6, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It states what data is returned but does not disclose behavior such as read-only nature, rate limits, authentication requirements, or error handling for invalid IDs. Moderate 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 sentence that efficiently conveys the tool's purpose and key outputs with no redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has only one required parameter and no output schema, the description adequately covers the returned data (publications, metrics, coauthors). It is complete for a simple retrieval tool, though it could mention pagination or filtering if applicable.

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?

The schema already describes the scholarId parameter with 100% coverage. The description adds value by providing an example ID format, enhancing understanding beyond the schema alone.

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 the verb 'Get' and the resource 'Google Scholar author profile', listing specific outputs like publications, citation metrics (h-index, i10-index), and coauthors. It effectively distinguishes from sibling tools like search_author and list_papers.

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 detailed author information by ID but lacks explicit guidance on when to use this tool over alternatives like search_author for finding IDs or list_papers for paper lists. No exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server