Teamwork

Official

Overview Schema Source Related Servers Discussions Admin

twprojects-list_skills

Read-only

List and search Teamwork skills with filtering, pagination, and field selection. Count total skills or fetch only IDs and names for quick scanning.

Instructions

List skills.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number for pagination of results (1-based).
`fields`	No	The attributes to return for each skill, from the listed names.
`verbose`	No	If false, returns id + name only — useful when scanning many results.
`page_size`	No	Number of results per page for pagination (1-500).
`count_only`	No	If true, return only {"count": N}: the exact number of matching skills, no rows — use for "how many". Ignores page, page_size, verbose, fields.
`order_mode`	No	The direction to sort the results in.
`search_term`	No	A search term to filter skills by name, or assigned users. The skill will be selected if each word of the term matches the name, or assigned user first or last name, not requiring that the word matches are in the same field.

Output Schema

TableJSON Schema

Name	Required	Description
`meta`	No
`count`	No	Exact number of matches across every page. Returned instead of the rows when count_only.
`skills`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv1.39.3Sep 9, 2026

removedInput schema / properties / count_only / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / count_only / type
```
Added value: +"boolean"
```

removedInput schema / properties / fields / anyOf

Removed value: -[
-  {
-    "items": {
-      "enum": [
-        "id",
-        "name",
-        "createdByUser",
-        "createdAt",
-        "updatedByUser",
-        "updatedAt",
-        "deletedByUser",
-        "deletedAt",
-        "users"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / fields / items

Added value: +{
+  "enum": [
+    "id",
+    "name",
+    "createdByUser",
+    "createdAt",
+    "updatedByUser",
+    "updatedAt",
+    "deletedByUser",
+    "deletedAt",
+    "users"
+  ],
+  "type": "string"
+}

addedInput schema / properties / fields / type
```
Added value: +"array"
```

removedInput schema / properties / order_mode / anyOf

Removed value: -[
-  {
-    "enum": [
-      "asc",
-      "desc"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / order_mode / enum
```
Added value: +[
+  "asc",
+  "desc"
+]
```
addedInput schema / properties / order_mode / type
```
Added value: +"string"
```

removedInput schema / properties / page / anyOf

Removed value: -[
-  {
-    "minimum": 1,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / page / minimum
```
Added value: +1
```
addedInput schema / properties / page / type
```
Added value: +"integer"
```

removedInput schema / properties / page_size / anyOf

Removed value: -[
-  {
-    "maximum": 500,
-    "minimum": 1,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / page_size / maximum
```
Added value: +500
```
addedInput schema / properties / page_size / minimum
```
Added value: +1
```
addedInput schema / properties / page_size / type
```
Added value: +"integer"
```

removedInput schema / properties / search_term / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / search_term / type
```
Added value: +"string"
```

removedInput schema / properties / verbose / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / verbose / type
```
Added value: +"boolean"
```

Changed4 schema fields changedv1.31.0Aug 19, 2026

addedInput schema / properties / count_only

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": false,
+  "description": "If true, return only {\"count\": N}: the exact number of matching skills, no rows — use for \"how many\". Ignores page, page_size, verbose, fields."
+}

addedInput schema / properties / order_mode

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "asc",
+        "desc"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The direction to sort the results in."
+}

addedOutput schema / properties / count

Added value: +{
+  "description": "Exact number of matches across every page. Returned instead of the rows when count_only.",
+  "type": "integer"
+}

addedOutput schema / properties / meta / properties / page / properties / count
```
Added value: +{
+  "type": [
+    "null",
+    "integer"
+  ]
+}
```

Changed1 schema field changedv1.27.2Aug 10, 2026

addedInput schema / properties / fields

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "enum": [
+          "id",
+          "name",
+          "createdByUser",
+          "createdAt",
+          "updatedByUser",
+          "updatedAt",
+          "deletedByUser",
+          "deletedAt",
+          "users"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The attributes to return for each skill, from the listed names."
+}

Changed4 schema fields changedv1.26.5Aug 5, 2026

changedInput schema / properties / page / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / page / description

Previous value: -"Page number for pagination of results."New value: +"Page number for pagination of results (1-based)."

changedInput schema / properties / page_size / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 500,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / page_size / description

Previous value: -"Number of results per page for pagination."New value: +"Number of results per page for pagination (1-500)."

Addedv1.26.0Jul 30, 2026
Removedv1.25.0Jul 17, 2026

Changed1 schema field changedv1.20.3May 18, 2026

changedInput schema / properties / verbose / description

Previous value: -"If true (default), the response includes full entity details. If false, only a minimal subset of fields (typically an id and a name/title) is returned to reduce response size — useful when scanning many results to pick an id before fetching the full entity."New value: +"If false, returns id + name only — useful when scanning many results."

Changed12 schema fields changedv1.20.1May 15, 2026

addedInput schema / properties / verbose

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": true,
+  "description": "If true (default), the response includes full entity details. If false, only a minimal subset of fields (typically an id and a name/title) is returned to reduce response size — useful when scanning many results to pick an id before fetching the full entity."
+}

removedOutput schema / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / meta / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / meta / properties / page / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / meta / properties / page / required
```
Removed value: -[
-  "hasMore"
-]
```
removedOutput schema / properties / meta / required
```
Removed value: -[
-  "page"
-]
```
removedOutput schema / properties / skills / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / skills / items / properties / users / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / skills / items / properties / users / items / properties / meta / additionalProperties
```
Removed value: -true
```
removedOutput schema / properties / skills / items / properties / users / items / required
```
Removed value: -[
-  "id",
-  "type"
-]
```

removedOutput schema / properties / skills / items / required

Removed value: -[
-  "id",
-  "name",
-  "createdByUser",
-  "createdAt",
-  "updatedByUser",
-  "updatedAt",
-  "deletedByUser",
-  "deletedAt",
-  "users"
-]

removedOutput schema / required

Removed value: -[
-  "meta",
-  "skills"
-]

Addedv1.18.3May 12, 2026
Removedv1.18.2May 11, 2026
Addedv1.17.2May 4, 2026

TDQS

B3.1/5.0

Behavior2/5

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

The description only restates the basic operation and adds no behavioral context beyond the annotations. The annotations already communicate readOnlyHint=true and destructiveHint=false, but the prose does not mention pagination, filtering defaults, or result-set semantics. As a safe read operation this is acceptable, but no additional behavioral disclosure is provided.

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 extremely short and contains no filler, making it easy to parse and front-loaded. It is concise, though perhaps too terse to add much guidance beyond the tool name.

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?

With a full output schema, complete parameter descriptions, and read-only annotations, the structured data provides most of what an agent needs to invoke the tool correctly. The description itself is minimal, so a bit more context about typical usage or result behavior would make it fully complete.

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%, so the input schema fully documents all seven parameters, including defaults, enums, and the count_only behavior. The description adds no parameter-level meaning; the schema carries the load, which matches the baseline of 3.

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?

The description clearly states the operation ('List') and the resource ('skills'), so an agent can understand the basic purpose. However, it does not elaborate on scope or distinguish itself from sibling list_* tools beyond the resource name, making it clear but without explicit sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives like twprojects-get_skill, twprojects-create_skill, or other list_* tools. There is no mention of exclusions, prerequisites, or conditions that would route an agent to this tool, so usage must be inferred entirely from the name and schema.

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

Deploy Server