jira_get_project
Retrieve Jira project details by key to access project metadata, configuration, and identifiers for issue tracking or integration tasks.
Instructions
Get project details
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": {
"key": "<key>"
},
"name": "jira_get_project"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | project key, e.g. PROJ |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Jira id; Server sends ids as strings, numeric ones included | |
| key | Yes | project key, e.g. PROJ | |
| lead | No | user reference; Server uses `name`, Cloud uses `accountId` | |
| name | No | project name | |
| self | No | absolute URL of this resource on the instance | |
| roles | No | role name -> role URL | |
| expand | No | which optional sections the server inlined in this response | |
| archived | No | true when the project is archived | |
| versions | No | version array, when the response expands it | |
| avatarUrls | No | project avatar URLs keyed by size | |
| components | No | component array, when the response expands it | |
| issueTypes | No | issue-type array, when the response expands it | |
| description | No | project description, when set | |
| assigneeType | No | default assignee rule for the project | |
| projectTypeKey | No | software | service_desk | business | |
| projectCategory | No | the category this project belongs to, when it has one |