Skip to main content
Glama

twprojects-clone_project

Duplicate a project or instantiate one from a template with options to rename, shift dates, or assign to a different company.

Instructions

Clone/copy an existing project or instantiate one from a template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the project to clone.
nameNoThe name of the new cloned project. If not provided, the name of the original project will be used with an incremental suffix (e.g., 'Project Name (1)').
company_idNoThe ID of the company associated with the new cloned project. If not provided, the company of the original project will be used.
days_offsetNoDaysOffset is the number of days to shift all scheduled dates in the cloned project relative to the base date. When cloning from a template, it defines the project duration span. When copying an existing project, it shifts the original start and end dates by this many days. If omitted, calculated automatically from the source project's date range.
descriptionNoThe description of the new cloned project. If not provided, the description of the original project will be used.
target_dateNoDesired start or end date for the cloned project (chosen by template_date_target). Only applies when new_from_template=true. Format: YYYYMMDD. Defaults to today.
to_templateNoIndicates whether the new project should be set as a template.
new_from_templateNoIndicates whether the new project should be a regular one created from a template.
template_date_targetNoSpecifies whether target_date represents the project's start or end date. When 'end', the start date is calculated by subtracting the template project's duration from target_date. Only applicable when new_from_template=true.start
Behavior2/5

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

Annotations indicate readOnlyHint=false (modifies state) and idempotentHint=false. The description does not disclose side effects, such as what properties are copied or permissions needed. It only hints at date shifting via parameter descriptions, but overall transparency is minimal.

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 a single, front-loaded sentence. It is concise and to the point, though it could be slightly more structured. Every word earns its place, but it lacks details that could improve completeness without being verbose.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 parameters and no output schema, the description is too brief. It does not explain return values, error conditions, or what happens to dependent objects. For a complex mutation tool, this is insufficient for an agent to use reliably.

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?

The input schema has 100% description coverage, so the schema already explains each parameter. The description adds no extra meaning beyond 'clone/copy' and 'instantiate from template'. Baseline 3 is appropriate as schema covers meaning.

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 clearly states the tool's two main use cases: cloning an existing project or instantiating from a template. The verb 'clone' and phrase 'instantiate from a template' precisely indicate the action. Among siblings like 'create_project' and 'create_project_template', this tool is distinct for copying, making purpose unambiguous.

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 description implies when to use the tool (to copy a project or create from template) but does not explicitly state when to avoid it or contrast with alternatives like 'create_project'. No guidance on prerequisites or exclusions is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Teamwork/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server