Salesforce AI Agent MCP Server

jira_update_story_status

Update a Jira story's status to advance it through the workflow. Provide the issue key and target status to trigger the transition.

Instructions

Transition a Jira story to a new status. The available transitions depend on the current workflow configuration. Common statuses: 'To Do', 'In Progress', 'In Review', 'Done', 'Blocked'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issueKey": "<issueKey>",
      "targetStatus": "<targetStatus>"
    },
    "name": "jira_update_story_status"
  }
}

Input Schema

Name	Required	Description	Default
`issueKey`	Yes	Jira issue key (e.g. SFDC-123)
`targetStatus`	Yes	The target workflow status name (e.g. 'In Progress', 'Done', 'Blocked'). Must match an available transition exactly.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for disclosing side effects. It only states that transitions are workflow-dependent, which is a useful constraint, but it omits any information about permissions, reversibility, or what the operation returns. This is minimal behavioral disclosure for a mutation tool.

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 two sentences long, front-loaded with the primary action, and includes a useful note about workflow dependency. Every sentence contributes meaning without unnecessary padding.

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?

The description covers the core purpose and acknowledges workflow variability, but it does not explain how to discover available transitions or what the tool returns. Given the lack of an output schema and the absence of guidance on preconditions, the description is adequate but not fully self-sufficient.

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?

The input schema already provides detailed descriptions for both parameters, including format examples and exact-match requirements. The tool description adds no additional parameter information beyond restating common statuses already listed in the schema. With 100% schema coverage, the baseline of 3 is appropriate.

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 the tool's function with a specific verb ('Transition') and resource ('a Jira story'). It distinguishes from sibling tools like jira_get_story and jira_post_comment by focusing on status changes.

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

Usage Guidelines3/5

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

The description provides context that transitions depend on workflow configuration, implying the agent may need to check the current status first. However, it does not explicitly mention when to use this tool versus alternatives or give exclusions. No alternatives are named, so it earns a mid-level score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server