Skip to main content
Glama
smaniches

Semantic Scholar MCP Server

by smaniches
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

semantic_scholar_bulk_search

Read-onlyIdempotent

Search large sets of academic papers with sorting and cursor-based pagination. Use boolean queries and filters to retrieve every result page by page.

Instructions

Search papers with sorting and cursor-based pagination for large result sets.

Unlike regular search, supports sorting (e.g., by citation count), boolean
query syntax, and returns a continuation token for paging through all
results. The observed endpoint ignores ``limit`` and may return up to 1000
papers per page; the full page is returned so no row is skipped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.18
    • changedInput schema / $defs / BulkSearchInput / properties / limit / description
      Previous value: -"Max results per page (1-1000)"New value: +"Requested page size (1-1000), forwarded to the API. The observed bulk endpoint ignores it and returns up to 1000 papers per page; the whole page is returned (never truncated) so the continuation token skips nothing"
    • changedInput schema / $defs / BulkSearchInput / properties / query / description
      Previous value: -"Search query"New value: +"Search query. The bulk endpoint documents boolean syntax: + (AND), | (OR), - (NOT), \"quoted phrase\", * (prefix), ( ) grouping, ~N (edit distance / phrase slop), e.g. '\"graph neural network\" + drug'"
  2. Changed1 schema field changedv1.2.13
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "bulk_searchOutput",
-  "type": "object"
-}New value: +null
  3. Changed2 schema fields changedv1.2.6
    • addedInput schema / $defs / BulkSearchInput / properties / api_key / deprecated
      Added value: +true
    • changedInput schema / $defs / BulkSearchInput / properties / api_key / description
      Previous value: -"API key (overrides SEMANTIC_SCHOLAR_API_KEY env var)"New value: +"API key (overrides SEMANTIC_SCHOLAR_API_KEY env var). Deprecated: prefer the environment variable. Removal planned for v2.0.0."
  4. Addedv1.0.3

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the observed endpoint ignores `limit`, may return up to 1000 papers per page, and returns the full untruncated page so the continuation token skips nothing. No auth or rate-limit info, but this is strong operational disclosure.

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?

Three tight sentences with the core capability front-loaded and the pagination caveat last. Slight redundancy with the schema on boolean syntax and the ignored `limit` keeps it from being maximally efficient.

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?

No output schema exists, so the description carries the return-shape burden and does so partially by explaining the continuation token and full-page return. Combined with the rich nested schema and annotations, an agent has enough to invoke it correctly; exact paper fields returned remain unspecified.

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's nested properties are documented, but the single top-level `params` wrapper is not. The description clarifies the sort capability, boolean query syntax, and the continuation-token semantics of pagination, and flags the `limit` caveat. Some of this (boolean syntax, limit-ignored) duplicates the nested schema descriptions, limiting the added value.

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?

States a specific verb and resource ("Search papers") plus its distinguishing scope: sorting and cursor-based pagination for large result sets. It contrasts with "regular search" functionality but never names the sibling tool it is contrasted against, so differentiation relies on inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear routing condition: use this when you need sorting, boolean query syntax, or paging through a large result set, as opposed to regular search. No explicit when-not-to-use or named alternative is given, but the context is unambiguous.

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

Deploy Server

Other Tools