Skip to main content
Glama

twprojects-list_message_replies

Read-only

List replies under Teamwork message threads. Filter by message or project IDs, paginate results, and search reply body or title.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
message_idsNoFilter by message.
pageNoPage number for pagination of results.
page_sizeNoNumber of results per page for pagination.
project_idsNoFilter by project.
search_termNoA 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.
verboseNoIf false, returns id + name only — useful when scanning many results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNo
messageRepliesNo
Behavior2/5

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

Annotations already indicate readOnlyHint=true, and the description adds minimal behavioral context beyond listing replies. It does not disclose pagination behavior, ordering, or limits, relying heavily on the schema.

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 extremely concise with two sentences, no wasted words, and front-loads the core purpose.

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?

Given the 6 parameters with full schema descriptions and an existing output schema, the description is adequate but lacks details on combining filters or expected results; it meets minimum requirements without being comprehensive.

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 coverage is 100%, so parameters are well-documented by schema. The description reiterates the main filters (message_ids, project_ids) but adds no extra meaning beyond what the schema provides.

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 action 'List replies under a message thread' and specifies filtering options, effectively distinguishing it from siblings like 'get_message_reply' or 'list_messages'.

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 does not provide guidance on when to use this tool versus alternatives (e.g., get_message_reply for a single reply), nor does it mention conditions or exclusions.

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