Skip to main content
Glama

autotask_create_project

Create a new project in Autotask by specifying company, name, status, and project type. Optionally add description, dates, hours, and project lead.

Instructions

Create a new project in Autotask

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIDYesCompany ID for the project
projectNameYesProject name
descriptionNoProject description
statusYesProject status (1=New, 2=In Progress, 5=Complete)
startDateNoProject start date (YYYY-MM-DD)
endDateNoProject end date (YYYY-MM-DD)
projectLeadResourceIDNoProject manager resource ID
estimatedHoursNoEstimated hours for the project
projectTypeYesProject type (2=Proposal, 3=Template, 4=Internal, 5=Client, 8=Baseline). Required.

Implementation Reference

  • Schema definition for the 'autotask_create_project' tool. Defines input parameters: companyID, projectName, description, status, startDate, endDate, projectLeadResourceID, estimatedHours, projectType. Required fields: companyID, projectName, status, projectType.
    {
      name: 'autotask_create_project',
      description: 'Create a new project in Autotask',
      inputSchema: {
        type: 'object',
        properties: {
          companyID: {
            type: 'number',
            description: 'Company ID for the project'
          },
          projectName: {
            type: 'string',
            description: 'Project name'
          },
          description: {
            type: 'string',
            description: 'Project description'
          },
          status: {
            type: 'number',
            description: 'Project status (1=New, 2=In Progress, 5=Complete)'
          },
          startDate: {
            type: 'string',
            description: 'Project start date (YYYY-MM-DD)'
          },
          endDate: {
            type: 'string',
            description: 'Project end date (YYYY-MM-DD)'
          },
          projectLeadResourceID: {
            type: 'number',
            description: 'Project manager resource ID'
          },
          estimatedHours: {
            type: 'number',
            description: 'Estimated hours for the project'
          },
          projectType: {
            type: 'number',
            description: 'Project type (2=Proposal, 3=Template, 4=Internal, 5=Client, 8=Baseline). Required.'
          }
        },
        required: ['companyID', 'projectName', 'status', 'projectType']
      }
    },
  • Handler implementation for 'autotask_create_project'. Maps startDate/endDate (YYYY-MM-DD) to startDateTime/endDateTime (ISO format), then delegates to autotaskService.createProject().
    ['autotask_create_project', async (a) => {
      const projectData = { ...a };
      // Map startDate/endDate (YYYY-MM-DD) to startDateTime/endDateTime (ISO) expected by the API
      if (projectData.startDate && !projectData.startDateTime) {
        projectData.startDateTime = `${projectData.startDate}T00:00:00Z`;
        delete projectData.startDate;
      }
      if (projectData.endDate && !projectData.endDateTime) {
        projectData.endDateTime = `${projectData.endDate}T00:00:00Z`;
        delete projectData.endDate;
      }
      const id = await s.createProject(projectData); return { result: id, message: `Successfully created project with ID: ${id}` };
    }],
  • Service-layer createProject method. Calls AutotaskHttpClient.create('Projects', project) to POST to the Autotask REST API /Projects endpoint. Returns the new project ID.
    async createProject(project: Partial<AutotaskProject>): Promise<number> {
      const http = await this.ensureClient();
      try {
        this.logger.debug('Creating project:', project);
        const id = await http.create('Projects', project);
        this.logger.info(`Project created with ID: ${id}`);
        return id;
      } catch (error) {
        this.logger.error('Failed to create project:', error);
        throw error;
      }
    }
  • Registration of 'autotask_create_project' in the dispatch table (getDispatchTable method). Maps the tool name string to its async handler function.
    private getDispatchTable(): Map<string, (args: any) => Promise<{ result: any; message: string }>> {
      const s = this.autotaskService;
      type H = (args: any) => Promise<{ result: any; message: string }>;
Behavior2/5

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

No annotations provided, and the description adds no behavioral information beyond the action. It does not disclose side effects, permissions, uniqueness constraints, or response behavior, placing full burden on this minimal description.

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?

Extremely concise single sentence with no superfluous words. However, it could be slightly more informative without losing conciseness.

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?

For a tool with 9 parameters, 4 required, and no output schema or annotations, the description lacks completeness. It omits return values, error handling, and usage context, making it insufficient for an agent to fully understand the operation.

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 the schema already documents all parameters. The description adds no extra meaning beyond what the schema provides, achieving the baseline score.

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 'Create a new project in Autotask', using a specific verb and resource, and distinguishes well from sibling tools that create other entity types like tasks or phases.

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 on when to use this tool versus alternatives (e.g., autotask_update_project for modifications, or other creation tools). The description does not mention prerequisites or context.

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/wyre-technology/autotask-mcp'

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