Skip to main content
Glama

createComment

Add comments to tasks, milestones, notebooks, links, or file versions in Teamwork projects. Specify recipients, attach files, and set privacy for team communication.

Instructions

Creates a new comment for a specific resource (tasks, milestones, notebooks, links, fileversions) in Teamwork

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourceYesThe resource type (tasks, milestones, notebooks, links, fileversions)
resourceIdYesThe ID of the resource to add a comment to
bodyYesThe content of the comment
notifyNoWho to notify ('all' to notify all project users, 'true' to notify followers, specific user IDs, or empty for no notification)
isPrivateNoWhether the comment should be private
pendingFileAttachmentsNoComma-separated list of pending file references to attach to the comment
contentTypeNoContent type of the comment (html or plain text)plaintext
authorIdNoID of the user to post as (only for admins)

Implementation Reference

  • The handler function that executes the createComment tool logic. It processes the input parameters, constructs the comment data, calls the teamwork service to create the comment, and returns the result or error response.
    export async function handleCreateComment(input: any) {
      logger.info('Calling teamworkService.createComment()');
      logger.info(`Resource: ${input?.resource}, Resource ID: ${input?.resourceId}`);
      
      try {
        const resource = input.resource;
        const resourceId = input.resourceId;
        const commentData: any = {};
        
        // Set required fields
        commentData.body = input.body;
        
        // Set optional fields if provided
        if (input.notify !== undefined) commentData.notify = input.notify;
        if (input.isPrivate !== undefined) commentData['isprivate'] = input.isPrivate;
        if (input.pendingFileAttachments) commentData.pendingFileAttachments = input.pendingFileAttachments;
        if (input.contentType === 'html') commentData['content-type'] = 'html';
        if (input.authorId) commentData['author-id'] = input.authorId;
        
        const result = await teamworkService.createComment(resource, resourceId, commentData);
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify(result, null, 2)
          }]
        };
      } catch (error: any) {
        return createErrorResponse(error, 'Creating comment');
      }
    } 
  • The tool definition including name, description, input schema with properties and requirements, and annotations for the createComment tool.
    export const createCommentDefinition = {
      name: "createComment",
      description: "Creates a new comment for a specific resource (tasks, milestones, notebooks, links, fileversions) in Teamwork",
      inputSchema: {
        type: "object",
        properties: {
          resource: {
            type: "string",
            description: "The resource type (tasks, milestones, notebooks, links, fileversions)",
            enum: ["tasks", "milestones", "notebooks", "links", "fileversions"]
          },
          resourceId: {
            type: "string",
            description: "The ID of the resource to add a comment to"
          },
          body: {
            type: "string",
            description: "The content of the comment"
          },
          notify: {
            type: "string",
            description: "Who to notify ('all' to notify all project users, 'true' to notify followers, specific user IDs, or empty for no notification)",
            default: ""
          },
          isPrivate: {
            type: "boolean",
            description: "Whether the comment should be private",
            default: false
          },
          pendingFileAttachments: {
            type: "string",
            description: "Comma-separated list of pending file references to attach to the comment"
          },
          contentType: {
            type: "string",
            description: "Content type of the comment (html or plain text)",
            enum: ["html", "plaintext"],
            default: "plaintext"
          },
          authorId: {
            type: "string",
            description: "ID of the user to post as (only for admins)"
          }
        },
        required: ["resource", "resourceId", "body"]
      },
      annotations: {
        title: "Create Comment",
        readOnlyHint: false,
        destructiveHint: false,
        openWorldHint: false
      }
    };
  • The registration entry in the toolPairs array that associates the createComment tool definition with its handler function.
    { definition: createComment, handler: handleCreateComment },
  • The service function called by the tool handler to perform the actual API call to create a comment on the specified resource in Teamwork.
    export const createComment = async (resource: string, resourceId: string, commentData: any) => {
      try {
        // Validate resource type
        const validResources = ['tasks', 'milestones', 'notebooks', 'links', 'fileversions'];
        if (!validResources.includes(resource)) {
          throw new Error(`Invalid resource type. Must be one of: ${validResources.join(', ')}`);
        }
        
        // For API v1, we need the proper client
        const api = getApiClientForVersion('v1');
        
        // We're using the v1 API which has a different format for the request
        const payload = {
          comment: commentData
        };
        
        // The API v1 endpoint doesn't include the base path
        const response = await api.post(`/${resource}/${resourceId}/comments.json`, payload);
        
        return response.data;
      } catch (error: any) {
        logger.error(`Error creating comment for ${resource}/${resourceId}: ${error.message}`);
        throw new Error(`Failed to create comment for ${resource}/${resourceId}: ${error.message}`);
      }
    };
Behavior3/5

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

Annotations indicate this is a non-readOnly, non-destructive, non-openWorld operation. The description adds minimal behavioral context beyond annotations—it specifies the resource types but doesn't mention permissions (e.g., who can comment), rate limits, or side effects like notifications. With annotations covering basic safety, the description provides some value but lacks rich behavioral details.

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 a single, efficient sentence that clearly states the tool's purpose. It's front-loaded with the core action and resource scope, with no wasted words. However, it could be slightly more structured by explicitly listing the resource types rather than embedding them in parentheses.

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 8 parameters, 100% schema coverage, and annotations covering basic operations, the description is minimally adequate. It lacks output details (no output schema), doesn't explain error cases or permissions, and misses usage context. For a creation tool with multiple parameters, it should provide more guidance on successful 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%, with all parameters well-documented in the schema. The description adds no parameter-specific information beyond what's in the schema (e.g., it doesn't explain parameter interactions or provide examples). Baseline 3 is appropriate since the schema handles parameter documentation effectively.

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 action ('Creates a new comment') and target resources ('for a specific resource (tasks, milestones, notebooks, links, fileversions) in Teamwork'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate this tool from potential sibling comment-related tools (none are listed among siblings, but the description could still clarify uniqueness).

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 doesn't mention prerequisites (e.g., needing resource IDs), exclusions, or comparisons with other tools. The list of sibling tools includes various get/update/delete operations but no other comment creation tools, yet the description offers no contextual usage advice.

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/Vizioz/Teamwork-MCP'

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