Skip to main content
Glama

overleaf_git_sync

Sync Overleaf projects with local files through Git Bridge: clone, pull, check status, or push commits from AI coding agents.

Instructions

Run direct Git Bridge operations (clone, pull, status, push) for Paid/Institutional Overleaf projects.

Args: action: 'clone' or 'pull' (sync remote to local), 'status' (view diff & commits), or 'push' (stage, commit, push). project_id: 24-character Overleaf project ID or full Overleaf project URL. local_dir: Optional local checkout directory (defaults to ~/.cache/overleaf-mcp/repos/<project_id>). commit_message: Commit message when action='push'. paths: Optional specific relative paths to stage when action='push' (defaults to all changes).

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": {
      "action": "<action>",
      "project_id": "<project_id>"
    },
    "name": "overleaf_git_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsNo
actionYes
local_dirNo
project_idYes
commit_messageNoUpdate via Overleaf MCP Agent

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it does disclose the Paid/Institutional plan gate, the default local checkout location, and that 'push' stages, commits, and then pushes (an outward-mutating step). It does not say what credentials/auth the Git Bridge needs, whether push can overwrite remote history or fail on conflicts, or what happens to uncommitted local changes.

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?

Purpose is front-loaded in one sentence, then args are laid out in a clean per-parameter list with no filler prose. Slight redundancy in restating defaults already present in the schema (commit_message default, local_dir default), but nothing wasteful enough to obstruct an agent.

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

Completeness3/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, and the action semantics plus parameter meanings are covered for a 5-parameter tool. What is missing for a credential-dependent, multi-mode git tool is auth/setup context and failure modes (non-paid project, auth expired, push conflicts), which an agent would need to call this correctly.

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: it explains all five parameters, including the actionable detail that project_id accepts a 24-character ID OR a full Overleaf URL, that local_dir defaults to a cache path, that commit_message applies only to 'push', and that paths defaults to all changes. Remaining gaps are minor (e.g., path base directory, conflict behavior on pull).

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?

Names specific verbs (clone, pull, status, push) and the concrete resource (Overleaf projects via the Git Bridge), plus a plan constraint (Paid/Institutional). It is not tautological and gives an agent a clear picture of the operation, though it never distinguishes itself from the sibling overleaf_pull_project, which sounds like it does overlapping work.

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 per-action parentheticals give real selection guidance among the four actions ('pull' syncs remote to local, 'status' views diff & commits, 'push' stages/commits/pushes). However, there is no guidance on when to use this Git Bridge tool versus the API-based overleaf_pull_project or other file siblings, and no prerequisites (git token/credentials) are stated beyond the plan requirement.

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