Skip to main content
Glama

List Author Papers

get_author_papers
Read-onlyIdempotent

List an author's published papers, newest first, paged with limit and offset. Pass an author ID or profile URL to see what they have worked on recently.

Instructions

List what one author has published, newest first, one page at a time.

Use for "what has X worked on recently". Pass an author id or URL from search_lacuna(search_type="author") or from any paper's author list.

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": {
      "author_id_or_url": "<author_id_or_url>"
    },
    "name": "get_author_papers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
author_id_or_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds real behavioral detail beyond that: results are sorted newest-first and returned one page at a time. It stops short of describing page-size behavior, what happens when the author is unknown, or how pagination terminates.

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?

Two short sentences with the primary behavior front-loaded and the parameter sourcing second. No filler, no restating of the title.

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?

An output schema exists, so return values need no explanation here. The description covers purpose, ordering, pagination, and argument acquisition, which is nearly everything needed for a 3-parameter read tool; only explicit limit/offset semantics are absent.

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 description coverage is 0%, so the description must carry the load, and it does explain the required parameter's provenance (an id or URL from search_lacuna(search_type="author") or a paper's author list). The limit and offset parameters are only alluded to via "one page at a time," leaving their interplay and defaults to the schema.

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?

States a specific verb and resource ("List what one author has published") plus ordering ("newest first") and pagination granularity ("one page at a time"). This clearly separates it from author-adjacent siblings like get_author_context or get_author_directions, which would not return a publication list.

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 concrete use case in the user's own words ("what has X worked on recently"), which is strong selection guidance. It also tells the agent where the required argument comes from, but it does not state exclusions or name an alternative for broader/paper-level queries.

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