Teamwork

Official

by Teamwork

Overview Schema Source Related Servers Discussions Admin

Remote

twprojects-list_message_replies

Read-only

List replies under a message thread. Filter by message or project IDs to find specific discussions.

Instructions

List replies under a message thread. Filter by message_ids or project_ids.

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 message reply, from the listed names.
`verbose`	No	If false, returns id + name only — useful when scanning many results.
`order_by`	No	The field to sort the message replies by. Omit to keep the ordering the API applies by default.
`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 message replies, no rows — use for "how many". Ignores page, page_size, verbose, fields.
`order_mode`	No	The direction to sort the results in.
`message_ids`	No	Filter by message.
`project_ids`	No	Filter by project.
`search_term`	No	A search term to filter message replies by body or title. Each word from the search term is used to match against the message reply body or title. The message reply will be selected if each word of the term matches the message reply body or title, 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.
`messageReplies`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.41.0Sep 12, 2026

changedInput schema / properties / fields / items / enum

Previous value: -[
-  "id",
-  "body",
-  "author",
-  "message",
-  "meta",
-  "createdAt",
-  "updatedAt",
-  "status"
-]New value: +[
+  "id",
+  "body",
+  "author",
+  "message",
+  "meta",
+  "createdAt",
+  "updatedAt",
+  "status",
+  "attachments"
+]

addedOutput schema / properties / messageReplies / items / properties / attachments

Added value: +{
+  "items": {
+    "properties": {
+      "id": {
+        "type": "integer"
+      },
+      "meta": {
+        "type": "object"
+      },
+      "type": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

Changed28 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",
-        "body",
-        "author",
-        "message",
-        "meta",
-        "createdAt",
-        "updatedAt",
-        "status"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / fields / items

Added value: +{
+  "enum": [
+    "id",
+    "body",
+    "author",
+    "message",
+    "meta",
+    "createdAt",
+    "updatedAt",
+    "status"
+  ],
+  "type": "string"
+}

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

removedInput schema / properties / message_ids / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "integer"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / message_ids / items
```
Added value: +{
+  "type": "integer"
+}
```
addedInput schema / properties / message_ids / type
```
Added value: +"array"
```

removedInput schema / properties / order_by / anyOf

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

addedInput schema / properties / order_by / enum
```
Added value: +[
+  "createdat",
+  "id"
+]
```
addedInput schema / properties / order_by / type
```
Added value: +"string"
```

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 / project_ids / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "integer"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / project_ids / items
```
Added value: +{
+  "type": "integer"
+}
```
addedInput schema / properties / project_ids / type
```
Added value: +"array"
```

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"
```

Changed5 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 message replies, no rows — use for \"how many\". Ignores page, page_size, verbose, fields."
+}

addedInput schema / properties / order_by

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "createdat",
+        "id"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The field to sort the message replies by. Omit to keep the ordering the API applies by default."
+}

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",
+          "body",
+          "author",
+          "message",
+          "meta",
+          "createdAt",
+          "updatedAt",
+          "status"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The attributes to return for each message reply, 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

Changed3 schema fields changedv1.20.3May 18, 2026

changedInput schema / properties / message_ids / description

Previous value: -"A list of message IDs to filter message replies by messages"New value: +"Filter by message."

changedInput schema / properties / project_ids / description

Previous value: -"A list of project IDs to filter message replies by projects"New value: +"Filter by project."

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."

Changed19 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 / messageReplies / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / messageReplies / items / properties / author / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / messageReplies / items / properties / author / properties / meta / additionalProperties
```
Removed value: -true
```
- removedOutput schema / properties / messageReplies / items / properties / author / required
```
Removed value: -[
-  "id",
-  "type"
-]
```
- removedOutput schema / properties / messageReplies / items / properties / message / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / messageReplies / items / properties / message / properties / meta / additionalProperties
```
Removed value: -true
```
- removedOutput schema / properties / messageReplies / items / properties / message / required
```
Removed value: -[
-  "id",
-  "type"
-]
```
- removedOutput schema / properties / messageReplies / items / properties / meta / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / messageReplies / items / properties / meta / properties / permissions / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / messageReplies / items / properties / meta / properties / permissions / required
```
Removed value: -[
-  "canEdit"
-]
```
- removedOutput schema / properties / messageReplies / items / properties / meta / required
```
Removed value: -[
-  "isRead",
-  "permissions"
-]
```
- removedOutput schema / properties / messageReplies / items / required
```
Removed value: -[
-  "id",
-  "body",
-  "author",
-  "message",
-  "createdAt",
-  "updatedAt",
-  "status"
-]
```
- 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 / required
```
Removed value: -[
-  "meta",
-  "messageReplies"
-]
```
Addedv1.18.3May 12, 2026
Removedv1.18.2May 11, 2026
Addedv1.17.2May 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that replies are 'under a message thread' and the available filters; it does not add behavioral context such as auth needs, rate limits, or pagination behavior beyond what annotations and schema provide.

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?

Two short, front-loaded sentences with zero waste. The core action is stated first, followed immediately by the key filter options.

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?

Given a fully described schema, an output schema, and annotations covering safety, the description provides enough to identify the tool and its primary filters. It does not mention pagination, count_only, search_term, or sorting, but those are documented in the schema and not required for correct invocation.

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 all 10 parameters are already documented with meaning in the schema. The description mentions message_ids and project_ids but adds no syntax, format, or interaction detail beyond what the schema states.

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 ('List') and resource ('replies under a message thread'), and names two filtering dimensions. It implicitly distinguishes from singular get_message_reply and from list_messages, but does not explicitly name or differentiate against sibling tools.

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 says it can be filtered by message_ids or project_ids, which is implied usage for a list tool. However, it gives no guidance on when to choose this over alternatives like list_messages or get_message_reply, and no exclusions.

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

Deploy Server