Skip to main content
Glama

getProjectsReportingUserTaskCompletion

Retrieve task completion reports for a specific user in Teamwork projects. Filter by date range, project, or team to analyze individual performance and project contributions.

Instructions

Returns task completions for a given user. Retrieve a person record and its task completion stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesPath parameter: userId
userTypeNouser type
updatedAfterNodate time
startDateNostart date for task completion report
endDateNoend date for task completion report
searchTermNofilter by comment content
reportFormatNodefine the format of the report
orderModeNoorder mode
orderByNoorder by
lastLoginAfterNoQuery parameter: lastLoginAfter
pageSizeNonumber of items in a page (not used when generating reports)
pageNopage number (not used when generating reports)
skipCountsNoSkipCounts allows you to skip doing counts on a list API endpoint for performance reasons.
showDeletedNoinclude deleted items
searchUserJobRoleNoInclude user job role in search
orderPrioritiseCurrentUserNoForce to have the current/session user in the response
onlySiteOwnerNoQuery parameter: onlySiteOwner
onlyOwnerCompanyNoreturn people only from the owner company. This will replace any provided company ID.
isReportDownloadNogenerate a report document
inclusiveFilterNomake the filter inclusive for user ids, teamIds, companyIds
includeServiceAccountsNoinclude service accounts
includePlaceholdersNoinclude placeholder users
includeCollaboratorsNoexclude collaborators types, returning only account and contact.
includeClientsNoinclude clients
includeArchivedProjectsNoinclude archived projects in the report
filterByNoCostRateNoReturns users who are missing cost rates(OCA only)
excludeContactsNoexclude contact types, returning only account and collaborator.
teamIdsNoteam ids
selectedColumnsNocustomise the report by selecting columns
projectIdsNofilter by project ids
jobRoleIdsNofilter by job role ids
includeNoinclude (not used when generating reports)
idsNofilter by user ids
fieldsTeamsNoQuery parameter: fields[teams]
fieldsPersonNoQuery parameter: fields[person]
fieldsPeopleNoQuery parameter: fields[people]
fieldsCompaniesNoQuery parameter: fields[companies]
fieldsProjectPermissionsNoQuery parameter: fields[ProjectPermissions]
excludeProjectIdsNoexclude people assigned to certain project id
excludeIdsNoexclude certain user ids
companyIdsNocompany ids

Implementation Reference

  • The tool handler function that executes the core logic: calls the reporting service with input and returns formatted JSON response or error.
    export async function handleGetProjectsReportingUserTaskCompletion(input: any) {
      try {
        const response = await getUserTaskCompletion(input);
        return {
          content: [{
            type: "text",
            text: JSON.stringify(response, null, 2)
          }]
        };
      } catch (error: any) {
        return createErrorResponse(error, 'Retrieving user task completion');
      }
    } 
  • The complete tool schema definition, including input parameters, descriptions, enums, and annotations for the MCP tool.
    export const getProjectsReportingUserTaskCompletionDefinition = {
      name: "getProjectsReportingUserTaskCompletion",
      description: "Returns task completions for a given user. Retrieve a person record and its task completion stats.",
      inputSchema: {
        type: 'object',
        properties: {
          userId: {
            type: 'integer',
            description: 'Path parameter: userId'
          },
          userType: {
            type: 'string',
            description: 'user type',
            enum: ['account', 'collaborator', 'contact']
          },
          updatedAfter: {
            type: 'string',
            description: 'date time'
          },
          startDate: {
            type: 'string',
            description: 'start date for task completion report'
          },
          endDate: {
            type: 'string',
            description: 'end date for task completion report'
          },
          searchTerm: {
            type: 'string',
            description: 'filter by comment content'
          },
          reportFormat: {
            type: 'string',
            description: 'define the format of the report'
          },
          orderMode: {
            type: 'string',
            description: 'order mode',
            enum: ['asc', 'desc']
          },
          orderBy: {
            type: 'string',
            description: 'order by',
            enum: ['id', 'name', 'namecaseinsensitive', 'overduetasks', 'assignedtasks', 'completedtasks', 'projects', 'activeprojects']
          },
          lastLoginAfter: {
            type: 'string',
            description: 'Query parameter: lastLoginAfter'
          },
          pageSize: {
            type: 'integer',
            description: 'number of items in a page (not used when generating reports)'
          },
          page: {
            type: 'integer',
            description: 'page number (not used when generating reports)'
          },
          skipCounts: {
            type: 'boolean',
            description: 'SkipCounts allows you to skip doing counts on a list API endpoint for performance reasons.'
          },
          showDeleted: {
            type: 'boolean',
            description: 'include deleted items'
          },
          searchUserJobRole: {
            type: 'boolean',
            description: 'Include user job role in search'
          },
          orderPrioritiseCurrentUser: {
            type: 'boolean',
            description: 'Force to have the current/session user in the response'
          },
          onlySiteOwner: {
            type: 'boolean',
            description: 'Query parameter: onlySiteOwner'
          },
          onlyOwnerCompany: {
            type: 'boolean',
            description: 'return people only from the owner company. This will replace any provided company ID.'
          },
          isReportDownload: {
            type: 'boolean',
            description: 'generate a report document'
          },
          inclusiveFilter: {
            type: 'boolean',
            description: 'make the filter inclusive for user ids, teamIds, companyIds'
          },
          includeServiceAccounts: {
            type: 'boolean',
            description: 'include service accounts'
          },
          includePlaceholders: {
            type: 'boolean',
            description: 'include placeholder users'
          },
          includeCollaborators: {
            type: 'boolean',
            description: 'exclude collaborators types, returning only account and contact.'
          },
          includeClients: {
            type: 'boolean',
            description: 'include clients'
          },
          includeArchivedProjects: {
            type: 'boolean',
            description: 'include archived projects in the report'
          },
          filterByNoCostRate: {
            type: 'boolean',
            description: 'Returns users who are missing cost rates(OCA only)'
          },
          excludeContacts: {
            type: 'boolean',
            description: 'exclude contact types, returning only account and collaborator.'
          },
          teamIds: {
            type: 'array',
            description: 'team ids'
          },
          selectedColumns: {
            type: 'array',
            description: 'customise the report by selecting columns'
          },
          projectIds: {
            type: 'array',
            description: 'filter by project ids'
          },
          jobRoleIds: {
            type: 'array',
            description: 'filter by job role ids'
          },
          include: {
            type: 'array',
            description: 'include (not used when generating reports)'
          },
          ids: {
            type: 'array',
            description: 'filter by user ids'
          },
          fieldsTeams: {
            type: 'array',
            description: 'Query parameter: fields[teams]'
          },
          fieldsPerson: {
            type: 'array',
            description: 'Query parameter: fields[person]'
          },
          fieldsPeople: {
            type: 'array',
            description: 'Query parameter: fields[people]'
          },
          fieldsCompanies: {
            type: 'array',
            description: 'Query parameter: fields[companies]'
          },
          fieldsProjectPermissions: {
            type: 'array',
            description: 'Query parameter: fields[ProjectPermissions]'
          },
          excludeProjectIds: {
            type: 'array',
            description: 'exclude people assigned to certain project id'
          },
          excludeIds: {
            type: 'array',
            description: 'exclude certain user ids'
          },
          companyIds: {
            type: 'array',
            description: 'company ids'
          }
        },
        required: ['userId']
      },
      annotations: {
        title: "Get the Tasks Completed by a User",
        readOnlyHint: false,
        destructiveHint: false,
        openWorldHint: false
      }
    };
  • Registration of the tool in the central toolPairs array used to create toolDefinitions and toolHandlersMap.
    { definition: getProjectsReportingUserTaskCompletion, handler: handleGetProjectsReportingUserTaskCompletion },
  • Import of the tool definition and handler from the specific reporting module.
    import { getProjectsReportingUserTaskCompletionDefinition as getProjectsReportingUserTaskCompletion, handleGetProjectsReportingUserTaskCompletion } from './reporting/getUserTaskCompletion.js';
  • Tool grouping configuration used for allow/deny filtering of tools.
    'Reporting': ['getProjectsReportingUserTaskCompletion', 'getProjectsReportingUtilization'],
Behavior3/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and openWorldHint=false, suggesting this is a non-destructive, closed-world read operation. The description adds context by mentioning 'task completion stats' and 'person record', implying it retrieves aggregated or statistical data rather than raw tasks. However, it does not disclose behavioral traits like rate limits, authentication needs, or whether it generates reports (hinted by parameters like isReportDownload). With annotations covering basic safety, the description adds 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 concise with two sentences: 'Returns task completions for a given user. Retrieve a person record and its task completion stats.' It is front-loaded with the main purpose and avoids unnecessary details. However, the second sentence is somewhat redundant with the first, slightly reducing efficiency.

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 tool's complexity (41 parameters, no output schema) and rich schema coverage, the description is minimally adequate. It states the purpose but does not cover output format, error handling, or how parameters like reportFormat affect behavior. Annotations provide basic safety info, but the description lacks completeness for such a parameter-heavy tool, leaving gaps in understanding its full context and usage.

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 the schema already documents all 41 parameters thoroughly. The description adds minimal semantics beyond the schema, mentioning 'user' and 'task completion stats', which loosely relate to parameters like userId and orderBy options. It does not explain parameter interactions or provide usage examples. Given high schema coverage, the baseline score of 3 is appropriate, as the description does not significantly enhance parameter understanding.

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: 'Returns task completions for a given user. Retrieve a person record and its task completion stats.' It specifies the verb ('returns', 'retrieve'), resource ('task completions', 'person record', 'task completion stats'), and scope ('for a given user'). However, it does not explicitly differentiate from sibling tools like getTasksMetricsComplete or getTasksMetricsLate, which might also involve task completion metrics.

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 does not mention any prerequisites, exclusions, or specific contexts for usage. For example, it does not clarify if this is for reporting purposes, real-time monitoring, or how it differs from other task-related tools in the sibling list.

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