Skip to main content
Glama

overleaf_pull_project

Download all files from an Overleaf project into a local workspace folder using ZIP web-session access or Git Bridge sync for free and paid accounts.

Instructions

Download/pull all files from an Overleaf project into a local workspace folder.

Args: project: Overleaf project ID, project URL, or exact project title. output_dir: Local directory where project files should be saved. method: 'zip' (works on Free & Paid accounts via Web Session) or 'git' (clones/pulls via Git Bridge).

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": {
      "project": "<project>",
      "output_dir": "<output_dir>"
    },
    "name": "overleaf_pull_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNozip
projectYes
output_dirYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the account/session mechanics behind each method, which is genuine behavioral context. It omits the operationally important facts: whether existing files in output_dir are overwritten, whether the directory is created if missing, and what auth state is required before calling.

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?

One purpose sentence followed by a tight Args block; every line carries information and the primary action is front-loaded. Minor redundancy in 'Download/pull' and the docstring formatting leaks implementation style rather than pure prose.

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 not be described. For a 3-parameter tool with zero schema coverage, the description covers the parameters and both transport modes adequately; the remaining gap is the destructive-on-disk behavior, which matters for a tool that writes many files locally.

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%, yet the description documents all three parameters, notably that 'project' accepts an ID, a URL, or an exact title, and that 'method' has two modes with different infrastructure. It stops short of explaining output_dir creation or collision behavior, which the schema also leaves undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it downloads/pulls all files from an Overleaf project into a local folder, which separates it from per-file siblings like overleaf_read_file and overleaf_list_files. The one ambiguity is the overlap with the sibling overleaf_git_sync when method='git', which the description never resolves.

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?

The method argument is given real decision context: 'zip' works on Free & Paid accounts via a web session, 'git' clones/pulls via the Git Bridge. That is useful routing between the two modes, but there is no guidance on when to prefer this bulk pull over overleaf_list_files/overleaf_read_file, and no mention of the auth prerequisite that overleaf_auth_status implies.

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