Skip to main content
Glama

overleaf_upload_file

Upload a single local file to an Overleaf project and automatically create any missing parent folders in the target remote path.

Instructions

Upload a single local file (.tex, .bib, .png, .pdf, .eps, etc.) to an Overleaf project.

Parent folders in remote_path are created automatically.

Args: project: Overleaf project ID, project URL, or exact project title. local_path: Path to the file on the local machine. remote_path: Target path in Overleaf (e.g. 'figures/arch.pdf'). Defaults to the local filename at root.

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>",
      "local_path": "<local_path>"
    },
    "name": "overleaf_upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes
local_pathYes
remote_pathNo

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 one real behavioral trait beyond the schema — 'Parent folders in remote_path are created automatically' — which is a genuine side effect an agent needs to know. It does not say what happens when the target file already exists (overwrite vs. fail), whether uploads require prior authentication, or any size limits.

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?

Front-loaded with the core action and the auto-folder-creation caveat, followed by a structured Args block. Every line adds information; there is no repetition of annotations and no filler.

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?

With 3 parameters, an existing output schema, and no annotations, the definition covers purpose, side effects, accepted file types, and all parameter meanings including the optional default. Remaining gaps — overwrite semantics and auth prerequisites — matter for a write tool but are modest given the output schema handles return values.

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 compensate, and it largely does: project is defined as ID, URL, or exact title; local_path is the local file path; remote_path is the target path with an example ('figures/arch.pdf') and its default ('local filename at root'). The only gap is that title matching ambiguity ('exact project title') is not spelled out.

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 ('Upload a single local file ... to an Overleaf project') and scopes it with 'single', which implicitly separates it from overleaf_upload_folder. It does not name a sibling outright, but the enumerated file types make the operation concrete enough to select on.

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?

Usage is only implied by 'single local file' — the agent can infer this is for one file and that overleaf_upload_folder handles bulk, but no when-to-use/when-not guidance is given. There is no mention of when to prefer overleaf_write_file for content already in memory, nor any stated prerequisites such as auth.

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