Skip to main content
Glama

clone_project

Copy an existing project, including its files, root document, and compiler, into a new named project. Start new work from a lab, journal, or team template without rebuilding it.

Instructions

Copy an existing project, its files, root document, and compiler included, into a new project with the given name. Overleaf gives the copy the account's default TeX Live image and spell-check language; set them with update_project_settings when they matter. Use it to start from a lab or journal template project.

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": {
      "sourceProjectId": "<sourceProjectId>",
      "name": "<name>"
    },
    "name": "clone_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesProject name, 1 to 150 characters without slashes
sourceProjectIdYesProject to copy

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only cover idempotency and destructiveness; the description adds meaningful behavior by disclosing that the copy inherits the account's default TeX Live image and spell-check language rather than the source project's settings. It does not mention permission requirements or name-collision failure modes, which keeps it short of a 5.

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?

Three tight sentences with the copy semantics front-loaded, then the settings caveat, then the use case. No sentence is 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?

An output schema exists, so return values need no explanation, and the description covers what gets copied, what defaults are reset, and the follow-up tool. The only gaps are authorization and duplicate-name behavior, which are minor for a two-parameter tool.

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

Parameters3/5

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

Schema coverage is 100%, with both name and sourceProjectId already documented including length and slash constraints. The description adds only that the name is 'given' and the source is an existing project, so the schema is doing the heavy lifting here.

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?

The description opens with a specific verb and resource ('Copy an existing project, its files, root document, and compiler included, into a new project') and states the scope of what is duplicated. This clearly separates it from create_project, which would start from nothing.

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?

It gives a concrete use case ('start from a lab or journal template project') and routes the agent to update_project_settings for TeX Live image and spell-check language after the copy. It does not explicitly contrast against create_project for empty-project scenarios, but the guidance is clear.

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