Skip to main content
Glama

PaperList

List papers in a conference

list_papers
Read-onlyIdempotent

Browse papers of one conference edition (e.g. conference="iclr", year=2025, or year=2027 for ICLR under-review submissions). Defaults to slim rows (id, title, conference, year, decision, rating_avg, url, short topics) with up to 250 per page; pass fields=full for abstracts (max 25) or use get_paper. Optionally filter by acceptance type or topic slug. For keyword search use search_papers.

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": {
      "conference": "<conference>",
      "year": "<year>"
    },
    "name": "list_papers"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
limitNoResults per page. slim: search up to 200 (default 10), list_papers up to 250 (default 100). full: 1-25 (default 10).
topicNoTopic slug from list_conferences topics_for
cursorNonext_cursor from a previous call
fieldsNoslim (default for list_papers/search_papers/find_similar_papers) returns id, title, conference, year, decision, rating_avg, url, and short topics. Use full or get_paper/fetch for abstracts. Prefer slim when scanning or exporting a conference.
decisionNoAcceptance types to keep (case-insensitive exact match). Common values: Oral, Spotlight, Poster, Highlight, Findings, Main; ICLR 2027 also uses Under review, Desk reject, Withdrawn.
conferenceYesConference slug, e.g. iclr

Output Schema

NameRequiredDescriptionDefault
noteNo
yearNo
totalNo
fieldsNo
papersYes
conferenceNo
next_cursorYesPass as cursor to get the next page; null when there are no more results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds real behavioral content: default slim projection and its exact columns, the 250-per-page cap for slim versus the 25 cap when fields=full, and the option to fall back to get_paper. It stops short of describing cursor/pagination behavior in prose, keeping it at a 4 rather than a 5.

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?

Three dense sentences, front-loaded with scope and examples before defaults and alternatives. Every clause carries information: example values, field projection, page caps, filters, and sibling routing.

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

Completeness5/5

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

With an output schema present, return values needn't be spelled out, yet the description still names the slim columns so an agent knows what it gets. Required parameters, filters, page limits, and sibling alternatives are all covered for a 7-parameter list tool.

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 coverage is 86%, so the baseline is 3 and the schema already documents limit, fields, decision, topic, and cursor. The description adds value beyond that by tying year=2027 to under-review submissions and by explaining the practical consequence of fields=full (abstracts, max 25).

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: browsing papers of a single conference edition, with concrete examples (conference="iclr", year=2025). It explicitly separates itself from search_papers (keyword search) and get_paper (abstracts), so an agent can choose it without opening a sibling schema.

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?

Gives explicit routing: use this for browsing one edition, search_papers for keyword search, get_paper for abstracts. It also flags the year=2027 case for ICLR under-review submissions, which is a non-obvious selection condition an agent would otherwise miss.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources