Skip to main content
Glama
dihannahdi

google-scholar-mcp

by dihannahdi

advanced_search

Perform advanced searches on Google Scholar with filters for author, source, year range, language, patents, review articles, and sort order.

Instructions

Perform an advanced search with full Google Scholar parameters: language, patents, review articles, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesMain search query
authorNoFilter by author name
sortByNoSort orderrelevance
sourceNoFilter by source/journal name
yearEndNoPublications up to this year
languageNoLanguage code (e.g., "en", "es", "zh-CN")en
yearStartNoPublications from this year onwards
numResultsNoNumber of results
includePatentsNoInclude patents in results
reviewArticlesOnlyNoOnly return review articles
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only lists parameters and mentions 'Google Scholar' but does not discuss expected behavior (e.g., search result format, rate limits, authentication needs). This omission leaves significant behavioral uncertainty.

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 a single concise sentence that packs key information without unnecessary elaboration. It front-loads the purpose and lists representative parameters efficiently.

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 has 10 parameters, no output schema, and no annotations, the description is too brief. It omits details about the output format, pagination, or how results are returned, which are essential for an advanced search 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?

Schema description coverage is 100%, so the baseline is 3. The description mentions a few parameter categories (language, patents, review articles) but adds no semantic value beyond the schema's existing parameter descriptions. It does not compensate for any gaps.

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 it performs an advanced search with Google Scholar parameters like language, patents, and review articles. This distinguishes it from simpler search tools (e.g., search_publications, search_author) but does not explicitly contrast them, hence 4.

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 when to use this tool: when you need advanced parameters such as language or patent filtering. However, it does not explicitly state when not to use it or mention alternative sibling tools, leaving the agent to infer usage context.

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/dihannahdi/google-scholar-mcp'

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