Skip to main content
Glama
expel-io

Atlassian Goals MCP Server

by expel-io

update_goal

Edit a goal's name, description, owner, dates, or archive status. Only supplied fields change; status and tags remain unaffected.

Instructions

Edit a goal's metadata — name, description, owner, target date, start date, or archive flag. Status changes are NOT done here; use post_goal_update to change status. Tag changes are also separate (use add_goal_tags / remove_goal_tags).

Only the fields you supply are changed; all others are left alone. At least one editable field is required.

Markdowndescription accepts markdown and is converted to ADF before send.

Owner — pass an Atlassian account ID (the same value that comes back from get_goal as owner.accountId).

Archivearchived: true archives the goal (hides it from active lists); archived: false unarchives. This is destructive in effect — confirm with the user before archiving real goals.

Example

update_goal({
  goalId: "ari:cloud:townsquare:...:goal/abc",
  name: "Renamed goal",
  description: "## New description\nUpdated context here.",
  targetDate: { date: "2026-12-31", confidence: "QUARTER" }
})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew goal name (plain text)
dryRunNoIf true, return the resolved mutation payload without submitting
goalIdYesGoal ARI (format: ari:cloud:townsquare:{cloudId}:goal/{uuid})
ownerIdNoNew owner — pass an Atlassian account ID (e.g. "712020:user-uuid-here")
archivedNoSet true to archive the goal, false to unarchive. Destructive in effect — confirm before archiving.
startDateNoNew start date (YYYY-MM-DD)
targetDateNoNew target date
descriptionNoNew goal description (markdown supported, converted to ADF)
Behavior5/5

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

With no annotations, the description fully carries the burden. It discloses that only supplied fields change (partial update), that markdown is converted to ADF, that archiving is destructive in effect, and that owner takes an Atlassian account ID. These are non-obvious behaviors beyond what the schema states.

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 longer than average but front-loaded with purpose, then exclusions, then behaviors, and a helpful example. Every section adds value; the bulleted structure aids scanning. Slightly verbose but earns its space.

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?

For a mutation tool with 8 parameters, no annotations, and no output schema, the description covers essential context: partial update semantics, exclusions, destructive archive, markdown conversion, owner ID format, and a realistic example. This is complete enough for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaningful context beyond the schema: owner account ID type, destructive archive semantics, markdown conversion, and a concrete example with targetDate structure. Some params like startDate rely on schema alone, but the extra guidance elevates the 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 opens with a specific verb and resource: 'Edit a goal's metadata' and enumerates the editable fields. It explicitly distinguishes from sibling tools by stating status changes go through post_goal_update and tag changes via add/remove_goal_tags, making the purpose unambiguous.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance with named alternatives ('Status changes are NOT done here; use post_goal_update... Tag changes are also separate...'). Also states the requirement of at least one editable field and warns to confirm before archiving, giving clear conditions for use.

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/expel-io/atlassian-goals-mcp'

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