Skip to main content
Glama

overleaf_list_projects

Lists all projects in your Overleaf account with IDs, titles, and editor URLs; optionally include archived or trashed projects to locate and open them.

Instructions

List all Overleaf projects in the user's account with IDs, titles, and editor URLs.

Args: include_archived: Include archived projects. include_trashed: Include trashed projects.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "overleaf_list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_trashedNo
include_archivedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does convey that this is a read-only enumeration and that archived and trashed projects are excluded by default via the flag documentation. It omits pagination/result-size behavior, permission or auth requirements, and whether the editor URLs are account-scoped — meaningful gaps for a tool that may be called against a large account.

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 behavior in the first sentence, then a compact Args block. The Args lines are near-tautological with the parameter names, so they earn only marginal space, but nothing is verbose or buried.

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?

The tool is simple (zero required params) and an output schema exists, so return-format explanation is optional; the description nonetheless names the returned fields. The remaining gap is the absence of any note about authentication state or result-set size, which matters for an account-wide listing.

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 description coverage is 0%, so the description must explain both flags, and it does list include_archived and include_trashed with one-line meanings. However, those lines largely restate the parameter names and add no detail on default behavior, interaction between the two filters, or what happens when both are true.

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 ('List all Overleaf projects in the user's account') and even names the fields returned (IDs, titles, editor URLs). The resource 'projects' inherently separates it from siblings like overleaf_list_files, though no alternative is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus overleaf_list_files, overleaf_auth_status, or overleaf_create_project, and no prerequisites such as whether authentication must be configured first. The only usage-relevant content is the two optional flags, which are parameter documentation rather than routing guidance.

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