Skip to main content
Glama
jina-ai

Jina AI Remote MCP Server

Official
by jina-ai

search_ssrn

Find academic papers and preprints on SSRN for social sciences, economics, law, finance, and humanities research.

Instructions

Search academic papers and preprints on SSRN (Social Science Research Network). Perfect for finding research papers in social sciences, economics, law, finance, accounting, management, and humanities. Use this when researching social science topics, looking for working papers, or finding the latest research in business and economics fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesAcademic search terms, author names, or research topics (e.g., 'corporate governance', 'behavioral finance', 'contract law'). Can be a single query string or an array of queries for parallel search.
numNoMaximum number of academic papers to return, between 1-100
tbsNoTime-based search parameter, e.g., 'qdr:h' for past hour, can be qdr:h, qdr:d, qdr:w, qdr:m, qdr:y

Implementation Reference

  • Core handler function that executes the SSRN search by making an API call to Jina AI's search endpoint with domain 'ssrn'.
    export async function executeSsrnSearch(
        searchArgs: SearchSsrnArgs,
        bearerToken: string
    ): Promise<SearchResultOrError> {
        try {
            const response = await fetch('https://svip.jina.ai/', {
                method: 'POST',
                headers: {
                    'Accept': 'application/json',
                    'Content-Type': 'application/json',
                    'Authorization': `Bearer ${bearerToken}`,
                },
                body: JSON.stringify({
                    q: searchArgs.query,
                    domain: 'ssrn',
                    num: searchArgs.num || 30,
                    ...(searchArgs.tbs && { tbs: searchArgs.tbs })
                }),
            });
    
            if (!response.ok) {
                return { error: `SSRN search failed for query "${searchArgs.query}": ${response.statusText}` };
            }
    
            const data = await response.json() as any;
            return { query: searchArgs.query, results: data.results || [] };
        } catch (error) {
            return { error: `SSRN search failed for query "${searchArgs.query}": ${error instanceof Error ? error.message : String(error)}` };
        }
    }
  • TypeScript interface defining the input schema for search_ssrn tool arguments.
    export interface SearchSsrnArgs {
        query: string;
        num?: number;
        tbs?: string;
    }
  • MCP tool registration for 'search_ssrn', including Zod input schema validation, tool description, and async handler that supports single or parallel queries via executeSsrnSearch.
    if (isToolEnabled("search_ssrn")) {
    	server.tool(
    		"search_ssrn",
    		"Search academic papers and preprints on SSRN (Social Science Research Network). Perfect for finding research papers in social sciences, economics, law, finance, accounting, management, and humanities. Use this when researching social science topics, looking for working papers, or finding the latest research in business and economics fields.",
    		{
    			query: z.union([z.string(), z.array(z.string())]).describe("Academic search terms, author names, or research topics (e.g., 'corporate governance', 'behavioral finance', 'contract law'). Can be a single query string or an array of queries for parallel search."),
    			num: z.number().default(30).describe("Maximum number of academic papers to return, between 1-100"),
    			tbs: z.string().optional().describe("Time-based search parameter, e.g., 'qdr:h' for past hour, can be qdr:h, qdr:d, qdr:w, qdr:m, qdr:y")
    		},
    		async ({ query, num, tbs }: { query: string | string[]; num: number; tbs?: string }) => {
    			try {
    				const props = getProps();
    
    				const tokenError = checkBearerToken(props.bearerToken);
    				if (tokenError) {
    					return tokenError;
    				}
    
    				// Handle single query or single-element array
    				if (typeof query === 'string' || (Array.isArray(query) && query.length === 1)) {
    					const singleQuery = typeof query === 'string' ? query : query[0];
    					const searchResult = await executeSsrnSearch({ query: singleQuery, num, tbs }, props.bearerToken);
    
    					return {
    						content: formatSingleSearchResultToContentItems(searchResult),
    					};
    				}
    
    				// Handle multiple queries with parallel search
    				if (Array.isArray(query) && query.length > 1) {
    					const searches = query.map(q => ({ query: q, num, tbs }));
    
    					const uniqueSearches = searches.filter((search, index, self) =>
    						index === self.findIndex(s => s.query === search.query)
    					);
    
    					const ssrnSearchFunction = async (searchArgs: SearchSsrnArgs) => {
    						return executeSsrnSearch(searchArgs, props.bearerToken);
    					};
    
    					const results = await executeParallelSearches(uniqueSearches, ssrnSearchFunction, { timeout: 30000 });
    
    					return {
    						content: formatParallelSearchResultsToContentItems(results),
    					};
    				}
    
    				return createErrorResponse("Invalid query format");
    			} catch (error) {
    				return createErrorResponse(`Error: ${error instanceof Error ? error.message : String(error)}`);
    			}
    		},
    	);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. While it mentions the platform (SSRN) and subject areas, it doesn't disclose behavioral traits like rate limits, authentication requirements, pagination behavior, error conditions, or what the return format looks like (since no output schema exists). The description adds some context about academic focus but lacks operational transparency.

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?

Two well-structured sentences that efficiently convey purpose and usage guidelines. The first sentence establishes core functionality, the second provides usage context. No wasted words, though it could be slightly more concise by combining some elements.

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

Completeness3/5

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

For a search tool with 3 parameters (100% schema coverage) but no annotations and no output schema, the description provides good purpose and usage context but lacks behavioral transparency about how results are returned, formatted, or limited. The absence of output schema means the description should ideally hint at return structure, which it doesn't.

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 schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema descriptions. Baseline 3 is appropriate when the schema does the heavy lifting, though no additional value is added.

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 specific verb ('Search') and resource ('academic papers and preprints on SSRN'), and distinguishes from siblings by specifying the academic/social sciences focus versus general web search (search_web) or other academic sources (search_arxiv). It explicitly mentions the Social Science Research Network platform.

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 when-to-use guidance: 'Perfect for finding research papers in social sciences, economics, law, finance, accounting, management, and humanities' and 'Use this when researching social science topics, looking for working papers, or finding the latest research in business and economics fields.' It implicitly distinguishes from parallel_search_ssrn by not mentioning parallel capabilities.

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/jina-ai/MCP'

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