Skip to main content
Glama
Teamwork

Teamwork

Official
by Teamwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

twprojects-clone_project

Clone an existing project or create one from a template in Teamwork, with options to adjust name, dates, description, and 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv1.39.3
    • removedInput schema / properties / company_id / anyOf
      Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / company_id / type
      Added value: +"integer"
    • removedInput schema / properties / days_offset / anyOf
      Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / days_offset / type
      Added value: +"integer"
    • removedInput schema / properties / description / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / description / type
      Added value: +"string"
    • removedInput schema / properties / name / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / name / type
      Added value: +"string"
    • removedInput schema / properties / new_from_template / anyOf
      Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / new_from_template / type
      Added value: +"boolean"
    • removedInput schema / properties / target_date / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / target_date / type
      Added value: +"string"
    • removedInput schema / properties / template_date_target / anyOf
      Removed value: -[
-  {
-    "enum": [
-      "start",
-      "end"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / template_date_target / enum
      Added value: +[
+  "start",
+  "end"
+]
    • addedInput schema / properties / template_date_target / type
      Added value: +"string"
    • removedInput schema / properties / to_template / anyOf
      Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / to_template / type
      Added value: +"boolean"
  2. Addedv1.26.0
  3. Removedv1.25.0
  4. Changed1 schema field changedv1.20.3
    • changedInput schema / properties / target_date / description
      Previous value: -"Target 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."New value: +"Desired 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."
  5. Addedv1.18.3
  6. Removedv1.18.2
  7. Addedv1.17.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive. The description adds the dual-mode behavior (cloning vs template instantiation) but does not disclose side effects such as what gets duplicated, whether timers/members are copied, or how template mode is triggered. No annotation contradiction exists.

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?

The description is a single front-loaded sentence with no filler words. It immediately presents the action and the two use cases, making it easy to parse.

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

Completeness3/5

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

With 9 parameters, two boolean mode switches, and no output schema, the high-level description is thin. It does not explain how an agent should indicate template vs project copying, what is returned, or what the clone includes. The schema compensates, but the description alone is not a complete entry point.

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% with rich per-parameter detail, so the tool description does not need to restate parameters. The description adds no parameter-level meaning beyond the schema, matching the baseline of 3.

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 names a specific action (clone/copy/instantiate) and resource (project), and the two modes (copy existing, instantiate from template) are distinct enough to separate it from create_project. It clearly tells an agent what the tool does at a glance.

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 the tool should be used when a project is being copied or created from a template, but it never explicitly states when to choose this over alternatives like create_project or create_project_template. No exclusion or alternative routing is provided.

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

Deploy Server

Other Tools