Skip to main content
Glama
Sign In
teamwork

teamwork

by sondv5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Teamwork: list task lists

list_tasklists
Read-only

Retrieve task lists (columns/boards) from a Teamwork project. Filter by list name or paginate results to locate the right board for organizing or updating tasks.

Instructions

List the task lists (columns/boards) inside a project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "list_tasklists"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
searchNoFilter by list name
pageSizeNo
projectIdYesTeamwork project id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds a small amount of context by equating task lists to 'columns/boards', but it discloses nothing about pagination, ordering, or response behavior.

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, focused sentence that front-loads the core operation and resource. The parenthetical clarification adds immediate value without waste.

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?

With no output schema and 50% parameter coverage, the description leaves important context missing: how pagination works, what the response looks like, and how search filters results. For an agent to invoke the tool correctly in non-trivial scenarios, additional field-level guidance is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, with page and pageSize lacking descriptions. The tool description does not compensate by explaining these parameters, their defaults, or their interaction. It only indirectly implies projectId through 'inside a project'.

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 uses a specific verb ('List'), a specific resource ('task lists'), and a clear scope ('inside a project'). The parenthetical '(columns/boards)' clarifies the domain-specific meaning, distinguishing it from other list-type tools like list_projects or list_tasks.

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 is given about when to use this tool versus alternatives such as list_tasks or get_task. The phrase 'inside a project' implies the projectId requirement, but there is no explicit mention of search or pagination usage nor any exclusion of sibling tools.

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