Skip to main content
Glama

Get paper citations

get_paper_citations
Read-onlyIdempotent

Retrieve papers that cite a given paper or the references it cites. Trace influence chains and follow-up work with pagination support.

Instructions

Use this when the user asks “what does this paper build on”, “what built on this”, traces influence chains, asks for follow-up work, or wants the lineage of an idea. direction=cited_by returns indexed papers that cite this one; direction=cites returns this paper's parsed references (which may or may not be in the corpus). Page with limit / offset; the response reports total and has_more so you can walk a large citation set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax citation edges to return per page (default 25, max 100).
offsetNoPagination offset; re-call with offset += limit while the response `has_more` is true. The response also reports `total`.
paper_idYesLune paper UUID, taken from a `search_papers` or `search_related_papers` result.
directionNo`cited_by`: indexed papers that cite this one (forward, follow-up work). `cites`: this paper's parsed references (back, what it built on).cited_by

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalNoTotal visible citation edges in this direction (paging count).
has_moreNoTrue when more edges exist past this page; re-call with offset += limit.
citationsYes
directionNo
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. Description adds important behavioral details: cites direction returns parsed references that may not be in corpus, and pagination behavior (total, has_more). No contradictions.

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 sentences, front-loaded with use cases, no wasted words. Essential information presented efficiently.

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 complete input schema, clear annotations, and output schema (presumed to document return fields), the description covers all necessary context: direction semantics, pagination, and appropriate use cases. No gaps.

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 100%, so baseline 3. Description adds value by explaining the meaning of direction values in terms of influence chains and clarifying pagination behavior, exceeding basic schema documentation.

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?

Description explicitly states the tool retrieves citations in two directions (cited_by and cites) and lists specific user queries it addresses (e.g., 'what does this paper build on', 'what built on this'). Clearly distinguishes from sibling tools like search_papers by detailing the citation-specific functionality.

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?

Provides clear use cases and explains the two directions and pagination. Does not explicitly state when not to use it or mention alternatives, but the context is clear enough for selection.

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/RetrogradeLabs/lune-mcp-server'

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