Skip to main content
Glama

twprojects-clone_project

Duplicate an existing project or create one from a template, with configurable dates, name, and description.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
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)').
new_from_templateNoIndicates whether the new project should be a regular one created from a template.
target_dateNoTarget date is the desired start or end date for the cloned project (determined by template_date_target). Used only when creating a project from a template (new_from_template=true). Accepted format: YYYYMMDD string. Defaults to the current user date if omitted.
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
to_templateNoIndicates whether the new project should be set as a template.
Behavior2/5

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

Annotations provide only title (Clone Project), no readOnlyHint or destructiveHint. The description does not disclose side effects (e.g., original project unchanged, what data is copied), permissions needed, or potential limits. Minimal transparency for a mutation tool.

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?

Single sentence, front-loaded with the two main use cases. No wasted words; efficient communication of purpose.

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?

Despite high schema coverage, the description is too short for the tool's complexity (9 parameters, two modes). It does not explain the difference between cloning and template instantiation, return value (no output schema), or what happens to the original project. Incomplete for a tool with this many parameters.

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 100% (all 9 parameters documented). Baseline 3 is appropriate as the tool description adds no additional parameter context beyond the schema. Description does not clarify parameter relationships or usage beyond schema.

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?

Description clearly states the tool clones/copies an existing project or creates from a template. Verb 'Clone' and resource 'project' are specific. It distinguishes from siblings like twprojects-create_project (create from scratch) and twprojects-create_project_template (create a template).

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?

No guidance on when to use this tool vs alternatives. For example, when to use twprojects-create_project instead. No mention of prerequisites or conditions for using each mode (clone vs template instantiation).

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