Skip to main content
Glama
its-dart

Dart MCP Server

by its-dart

list_task_comments

Retrieve and filter task comments in Dart by task ID, author, text, dates, or other parameters for efficient project management and analysis.

Instructions

List comments from Dart with optional filtering parameters. You can filter by author, task, text content, dates, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authorNoFilter by author name or email
authorIdNoFilter by author ID
idsNoFilter by comment IDs
limitNoNumber of results per page
offsetNoInitial index for pagination
parentIdNoFilter by parent comment ID
publishedAtAfterNoFilter by published date after (ISO format)
publishedAtBeforeNoFilter by published date before (ISO format)
taskNoFilter by task title
taskIdYesFilter by task ID
textNoFilter by comment text content

Implementation Reference

  • Handler logic for the 'list_task_comments' tool. Validates the taskId and calls CommentService.listComments with the provided arguments, returning the JSON-stringified comments.
    case LIST_TASK_COMMENTS_TOOL.name: {
      const taskId = getIdValidated(args.taskId, "taskId");
      const comments = await CommentService.listComments({ taskId, ...args });
      return {
        content: [{ type: "text", text: JSON.stringify(comments, null, 2) }],
      };
    }
  • Tool definition including name, description, and detailed inputSchema for 'list_task_comments' with properties for filtering comments by taskId (required), author, dates, etc.
    export const LIST_TASK_COMMENTS_TOOL: Tool = {
      name: "list_task_comments",
      description:
        "List comments from Dart with optional filtering parameters. You can filter by author, task, text content, dates, and more.",
      inputSchema: {
        type: "object",
        properties: {
          taskId: {
            type: "string",
            description: "Filter by task ID",
          },
          author: {
            type: "string",
            description: "Filter by author name or email",
          },
          authorId: {
            type: "string",
            description: "Filter by author ID",
          },
          ids: {
            type: "string",
            description: "Filter by comment IDs",
          },
          limit: {
            type: "number",
            description: "Number of results per page",
          },
          offset: {
            type: "number",
            description: "Initial index for pagination",
          },
          parentId: {
            type: "string",
            description: "Filter by parent comment ID",
          },
          publishedAtAfter: {
            type: "string",
            description: "Filter by published date after (ISO format)",
          },
          publishedAtBefore: {
            type: "string",
            description: "Filter by published date before (ISO format)",
          },
          task: {
            type: "string",
            description: "Filter by task title",
          },
          text: {
            type: "string",
            description: "Filter by comment text content",
          },
        },
        required: ["taskId"],
      },
    };
  • index.ts:192-214 (registration)
    Registration of all tools including LIST_TASK_COMMENTS_TOOL in the TOOLS array, which is returned by ListToolsRequestSchema handler.
    const TOOLS = [
      // Config
      GET_CONFIG_TOOL,
      // Tasks
      CREATE_TASK_TOOL,
      LIST_TASKS_TOOL,
      GET_TASK_TOOL,
      UPDATE_TASK_TOOL,
      DELETE_TASK_TOOL,
      // Docs
      CREATE_DOC_TOOL,
      LIST_DOCS_TOOL,
      GET_DOC_TOOL,
      UPDATE_DOC_TOOL,
      DELETE_DOC_TOOL,
      // Comments
      ADD_TASK_COMMENT_TOOL,
      LIST_TASK_COMMENTS_TOOL,
      // Other
      GET_DARTBOARD_TOOL,
      GET_FOLDER_TOOL,
      GET_VIEW_TOOL,
    ];
  • index.ts:371-373 (registration)
    Server request handler for listing tools, which exposes the registered TOOLS including 'list_task_comments'.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'List' implies a read operation, the description doesn't address critical behavioral aspects like pagination behavior (beyond mentioning parameters), rate limits, authentication requirements, or what happens when no comments match filters. It mentions filtering but lacks operational context.

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 appropriately concise with two sentences that efficiently communicate core functionality. The first sentence states the primary purpose, and the second highlights filtering capabilities. No wasted words, though it could be slightly more structured for clarity.

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?

Given 11 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain return format, error conditions, or operational constraints. For a complex filtering tool with rich parameters, more context about behavior and results is needed to guide effective use.

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%, providing detailed parameter documentation. The description adds minimal value by listing filter types (author, task, text content, dates) but doesn't explain parameter interactions, default behaviors, or provide examples beyond what's in the schema. With high schema coverage, baseline 3 is appropriate.

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 tool's purpose as 'List comments from Dart' with filtering capabilities, providing a specific verb ('List') and resource ('comments from Dart'). However, it doesn't explicitly differentiate from sibling tools like 'get_task' or 'add_task_comment', which would require a more specific distinction to earn a 5.

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. It mentions filtering parameters but doesn't specify scenarios where this tool is preferred over other comment-related operations or list operations like 'list_tasks'. No exclusions or prerequisites are mentioned.

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

Related 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/its-dart/dart-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server