overleaf-claude-mcp

Download the compiled PDF

overleaf_download_pdf

Compile an Overleaf LaTeX project and save the resulting PDF to a specified local path.

Instructions

Compile the project and save the resulting PDF locally.

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": {
      "destPath": "<destPath>"
    },
    "name": "overleaf_download_pdf"
  }
}

Input Schema

Name	Required	Description	Default
`destPath`	Yes
`projectId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 19, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the main side effects (compilation and local file save) but omits details such as overwrite behavior, failure handling, or whether the current project is used when projectId is omitted. This is moderate transparency but leaves important behavioral questions unanswered.

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?

The description is extremely concise at two short sentences with no filler. It front-loads the core action and is easy to parse, even if it is terse.

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

Completeness2/5

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

There is no output schema or annotations, so the description must cover return behavior and edge cases. It does not mention compile failures, whether the PDF is written to destPath, or how project selection works, making it incomplete for a side-effectful operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage for parameters, and the description does not explain destPath or projectId beyond the generic phrase 'save the resulting PDF locally.' While destPath is inferable from 'save locally,' projectId is entirely unaddressed, leaving the agent without guidance on which project to compile.

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 uses a specific verb phrase 'Compile the project and save the resulting PDF locally,' clearly stating both actions and the resource. This distinguishes it from sibling tools like overleaf_compile (which only compiles) and overleaf_download_file (which downloads arbitrary files without compiling).

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

Usage Guidelines3/5

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

No explicit when-to-use or alternative comparisons are provided. The description implies a combined compile-and-download workflow, but does not mention when to prefer this over calling overleaf_compile followed by overleaf_download_file, nor any prerequisites or exclusions.

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