Skip to main content
Glama

jira_list_projects

Read-onlyIdempotent

Lists Jira projects for a given site and account, with an optional name or key filter, so you can find the project to work with.

Instructions

List Jira projects, with an optional name query.

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": {
      "site": "<site>",
      "email": "<email>",
      "api_token": "<api_token>"
    },
    "name": "jira_list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesJira site (e.g. mycompany)
emailYesAtlassian account email
queryNoFilter projects by name or key
api_tokenYesAtlassian API token
max_resultsNoProjects to return (max 100, default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds little beyond restating the listing behavior; it omits pagination behavior (max_results default 50, cap 100) and any auth/rate context beyond what the schema implies.

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?

A single front-loaded sentence with no filler; the optional filter is mentioned after the core action. It is efficient, though extremely terse for a tool with auth requirements.

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?

No output schema, so the return shape (project fields available) is undisclosed, and the pagination behavior lives only in the schema. For a simple list tool with rich annotations this is acceptable but leaves gaps an agent must infer.

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 all five parameters are already documented (site, email, api_token, query, max_results with default/cap). The description's mention of an optional name query merely echoes the schema's query field, adding no new semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List Jira projects'), making the operation unambiguous. It does not distinguish itself from sibling Jira tools (jira_search_issues, jira_get_issue), but the resource is clear enough.

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 implies this is the tool for enumerating projects and mentions an optional name query, but gives no explicit when-to-use vs alternatives guidance or conditions for preferring the query filter over listing all.

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

Deploy Server

Other Tools