Skip to main content
Glama

aps_issues_update

Update an existing issue with optional fields like title, description, status, assignee, due date, and more. Requires data:write scope and project and issue IDs.

Instructions

Update an existing issue. Only include the fields you want to change. ⚠️ Requires 'data:write' in APS_SCOPE. To see which fields the current user can update, check permittedAttributes in the issue detail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID – accepts with or without 'b.' prefix.
issue_idYesIssue UUID to update.
titleNoNew title. Optional.
descriptionNoNew description. Optional.
statusNoNew status. Optional.
assigned_toNoNew assignee Autodesk ID. Optional.
assigned_to_typeNoAssignee type. Required if assigned_to is set.
due_dateNoNew due date (ISO8601). Optional.
start_dateNoNew start date (ISO8601). Optional.
location_idNoNew LBS location UUID. Optional.
location_detailsNoNew location text. Optional.
root_cause_idNoNew root cause UUID. Optional.
publishedNoSet published state. Optional.
watchersNoNew watcher list. Optional.
custom_attributesNoCustom attribute values to update. Optional.
regionNoData centre region. Defaults to US.

Implementation Reference

  • The handler function for 'aps_issues_update' tool. It validates project_id and issue_id, strips 'b.' prefix from project ID, builds a request body from provided optional fields (title, description, status, assigned_to, due_date, etc.), then sends a PATCH request to construction/issues/v1/projects/{pid}/issues/{issueId}. The response is summarized via summarizeIssueDetail.
    // ── aps_issues_update ───────────────────────────────────────
    if (name === "aps_issues_update") {
      const projectId = args.project_id as string;
      const issueId = args.issue_id as string;
      const e1 = validateIssuesProjectId(projectId);
      if (e1) return fail(e1);
      const e2 = validateIssueId(issueId);
      if (e2) return fail(e2);
    
      const pid = toIssuesProjectId(projectId);
      const region = args.region as string | undefined;
      const t = await token();
    
      const body: Record<string, unknown> = {};
      if (args.title != null) body.title = args.title;
      if (args.description != null) body.description = args.description;
      if (args.status != null) body.status = args.status;
      if (args.assigned_to && !args.assigned_to_type)
        return fail("assigned_to_type is required when assigned_to is provided.");
      if (args.assigned_to != null && args.assigned_to_type != null) {
        body.assignedTo = args.assigned_to;
        body.assignedToType = args.assigned_to_type;
      } else if (args.assigned_to_type != null) {
        body.assignedToType = args.assigned_to_type;
      }
      if (args.due_date != null) body.dueDate = args.due_date;
      if (args.start_date != null) body.startDate = args.start_date;
      if (args.location_id != null) body.locationId = args.location_id;
      if (args.location_details != null) body.locationDetails = args.location_details;
      if (args.root_cause_id != null) body.rootCauseId = args.root_cause_id;
      if (args.published != null) body.published = args.published;
      if (args.watchers != null) body.watchers = args.watchers;
      if (args.custom_attributes != null) body.customAttributes = args.custom_attributes;
    
      if (Object.keys(body).length === 0) {
        return fail("No fields to update. Provide at least one field to change.");
      }
    
      const raw = await apsDmRequest(
        "PATCH",
        `construction/issues/v1/projects/${pid}/issues/${issueId}`,
        t,
        { body, headers: issuesWriteHeaders(region) },
      );
      return json(summarizeIssueDetail(raw));
    }
  • src/index.ts:651-713 (registration)
    Registration of the 'aps_issues_update' tool in the TOOLS array. Defines the name, description, and inputSchema describing accepted parameters: project_id, issue_id, and optional fields like title, status, assigned_to, due_date, etc.
    // 15 ── aps_issues_update
    {
      name: "aps_issues_update",
      description:
        "Update an existing issue. Only include the fields you want to change. " +
        "⚠️ Requires 'data:write' in APS_SCOPE. " +
        "To see which fields the current user can update, check permittedAttributes in the issue detail.",
      inputSchema: {
        type: "object" as const,
        properties: {
          project_id: {
            type: "string",
            description: "Project ID – accepts with or without 'b.' prefix.",
          },
          issue_id: {
            type: "string",
            description: "Issue UUID to update.",
          },
          title: { type: "string", description: "New title. Optional." },
          description: { type: "string", description: "New description. Optional." },
          status: {
            type: "string",
            enum: ["draft", "open", "pending", "in_progress", "in_review", "completed", "not_approved", "in_dispute", "closed"],
            description: "New status. Optional.",
          },
          assigned_to: { type: "string", description: "New assignee Autodesk ID. Optional." },
          assigned_to_type: {
            type: "string",
            enum: ["user", "company", "role"],
            description: "Assignee type. Required if assigned_to is set.",
          },
          due_date: { type: "string", description: "New due date (ISO8601). Optional." },
          start_date: { type: "string", description: "New start date (ISO8601). Optional." },
          location_id: { type: "string", description: "New LBS location UUID. Optional." },
          location_details: { type: "string", description: "New location text. Optional." },
          root_cause_id: { type: "string", description: "New root cause UUID. Optional." },
          published: { type: "boolean", description: "Set published state. Optional." },
          watchers: {
            type: "array",
            items: { type: "string" },
            description: "New watcher list. Optional.",
          },
          custom_attributes: {
            type: "array",
            items: {
              type: "object",
              properties: {
                attributeDefinitionId: { type: "string" },
                value: {},
              },
              required: ["attributeDefinitionId", "value"],
            },
            description: "Custom attribute values to update. Optional.",
          },
          region: {
            type: "string",
            enum: ["US", "EMEA", "AUS", "CAN", "DEU", "IND", "JPN", "GBR"],
            description: "Data centre region. Defaults to US.",
          },
        },
        required: ["project_id", "issue_id"],
      },
    },
  • Helper functions used by the update handler: issuesHeaders() builds optional region headers, issuesWriteHeaders() adds Content-Type for PATCH requests.
    /** Build optional headers for Issues API calls. */
    function issuesHeaders(region?: string): Record<string, string> {
      const h: Record<string, string> = {};
      if (region) h["x-ads-region"] = region;
      return h;
    }
    
    /** Build headers for Issues API write operations (POST/PATCH). */
    function issuesWriteHeaders(region?: string): Record<string, string> {
      return { "Content-Type": "application/json", ...issuesHeaders(region) };
    }
  • The toIssuesProjectId helper strips the 'b.' prefix from project IDs, used by the update handler before making the API call.
    export function toIssuesProjectId(projectId: string): string {
      return projectId.replace(/^b\./, "");
    }
  • The summarizeIssueDetail helper transforms the raw API response into a compact IssueDetailSummary object, used by the update handler to return a clean result.
    /** Summarise a single issue response – keeps more detail than the list summary. */
    export function summarizeIssueDetail(raw: unknown): IssueDetailSummary {
      const issue = raw as Record<string, unknown>;
    
      const customAttrs = Array.isArray(issue.customAttributes)
        ? (issue.customAttributes as Record<string, unknown>[]).map((ca) => ({
            id: (ca.attributeDefinitionId as string) ?? "",
            value: ca.value,
            type: (ca.type as string) ?? undefined,
            title: (ca.title as string) ?? undefined,
          }))
        : undefined;
    
      const linkedDocs = Array.isArray(issue.linkedDocuments)
        ? issue.linkedDocuments.length
        : 0;
    
      return {
        id: issue.id as string,
        displayId: (issue.displayId as number) ?? 0,
        title: (issue.title as string) ?? "",
        description: (issue.description as string) ?? undefined,
        status: (issue.status as string) ?? "",
        issueTypeId: (issue.issueTypeId as string) ?? undefined,
        issueSubtypeId: (issue.issueSubtypeId as string) ?? undefined,
        assignedTo: (issue.assignedTo as string) ?? undefined,
        assignedToType: (issue.assignedToType as string) ?? undefined,
        dueDate: (issue.dueDate as string) ?? undefined,
        startDate: (issue.startDate as string) ?? undefined,
        locationId: (issue.locationId as string) ?? undefined,
        locationDetails: (issue.locationDetails as string) ?? undefined,
        rootCauseId: (issue.rootCauseId as string) ?? undefined,
        published: (issue.published as boolean) ?? false,
        commentCount: (issue.commentCount as number) ?? 0,
        createdBy: (issue.createdBy as string) ?? "",
        createdAt: (issue.createdAt as string) ?? "",
        updatedAt: (issue.updatedAt as string) ?? "",
        closedBy: (issue.closedBy as string) ?? undefined,
        closedAt: (issue.closedAt as string) ?? undefined,
        customAttributes: customAttrs,
        linkedDocumentCount: linkedDocs,
        watchers: Array.isArray(issue.watchers)
          ? (issue.watchers as string[])
          : undefined,
        permittedStatuses: Array.isArray(issue.permittedStatuses)
          ? (issue.permittedStatuses as string[])
          : undefined,
      };
    }
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the required write scope, partial update nature, and suggests checking permittedAttributes for user capabilities. It does not detail side effects but adequately warns about permissions.

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 extremely concise with two sentences plus a warning and tip. Every sentence adds value without redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given high schema coverage and no output schema, the description covers the key aspects: operation, partial update, required scope, and how to verify editable fields. It is complete for this tool's purpose.

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 baseline is 3. The description adds marginal value by stating 'Only include the fields you want to change' and requiring scope, but most parameter meanings are already clear from the schema.

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 'Update an existing issue', which is a specific verb+resource. It also mentions partial update semantics ('Only include the fields you want to change'), distinguishing it from related sibling tools like aps_issues_create or aps_issues_get.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context on when to use (updating issues) and mentions required scope ('Requires 'data:write' in APS_SCOPE') and a tip to check permittedAttributes. However, it does not explicitly state when not to use or mention alternatives among siblings.

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/EverseDevelopment/APS.MCP'

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