Skip to main content
Glama

create_project

Create a new Overleaf project from a blank or example template and return its projectId, URL, and root document path for editing or compiling.

Instructions

Create a new Overleaf project and return its projectId, url, and rootDocPath. A "blank" project still contains Overleaf's stub main.tex as its root document; after importing your own manuscript, point the project at it with update_project_settings or delete the stub with manage_entity. "example" seeds Overleaf's example paper.

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

Input Schema

NameRequiredDescriptionDefault
nameYesProject name, 1 to 150 characters without slashes
templateNoblank

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
projectIdYes
rootDocPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare idempotentHint=false and destructiveHint=false. The description adds useful behavior beyond that: a blank project still contains a stub main.tex, and example seeds Overleaf's example paper. It does not discuss permissions or auth requirements, but the behavioral context is otherwise strong.

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?

The description is front-loaded with the core action and return values, then adds template-specific behavior. It is efficient, though the sentence about updating settings or deleting the stub is somewhat dense.

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?

Given the simple two-parameter schema, existing output schema, and basic annotations, the description covers the key creation behavior and template consequences. It is nearly complete, with the main omission being any note about authentication or permissions needed to create a project.

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 only 50%, with the template enum lacking a schema description. The description compensates well by explaining what blank and example actually produce, though it adds no meaning beyond the schema for the name parameter.

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 states a specific verb and resource: create a new Overleaf project. It also names the returned identifiers (projectId, url, rootDocPath), making the operation concrete and distinguishable from project-management tools.

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 clear context for choosing between the blank and example templates and explains the next step after importing a manuscript. It does not explicitly state when to use this versus alternatives such as clone_project or import_project_zip, so it falls short of full when/when-not guidance.

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