Skip to main content
Glama
Sign In
atlassian-browser-mcp

atlassian-browser-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search Issues

jira_search
Read-onlyIdempotent

Search Jira issues using JQL to locate work by project, status, assignee, label, or priority. Returns matching issues with configurable fields and pagination.

Instructions

Search Jira issues using JQL (Jira Query Language).

Input Schema

NameRequiredDescriptionDefault
jqlYesJQL query string (Jira Query Language). Examples: - Find Epics: "issuetype = Epic AND project = PROJ" - Find issues in Epic: "parent = PROJ-123" - Find by status: "status = 'In Progress' AND project = PROJ" - Find by assignee: "assignee = currentUser()" - Find recently updated: "updated >= -7d AND project = PROJ" - Find by label: "labels = frontend AND project = PROJ" - Find by priority: "priority = High AND project = PROJ"
limitNoMaximum number of results (1-50)
expandNo(Optional) fields to expand. Examples: 'renderedFields', 'transitions', 'changelog'
fieldsNo(Optional) Comma-separated fields to return in the results. Use '*all' for all fields, or specify individual fields like 'summary,status,assignee,priority'assignee,created,description,issuetype,labels,priority,reporter,status,summary,updated,versions
start_atNoStarting index for pagination (0-based)
page_tokenNo(Optional) Pagination token from a previous search result. Cloud only — Server/DC uses start_at for pagination.
projects_filterNo(Optional) Comma-separated list of project keys to filter results by. Overrides the environment variable JIRA_PROJECTS_FILTER if provided.
use_display_namesNoWhen true, custom field keys in the output use human-readable display names (e.g. 'Story Points') instead of opaque IDs (e.g. 'customfield_10243'). The 'names' expansion is added automatically. Standard fields are unaffected.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.4.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / fields / default
      Previous value: -"labels,versions,priority,description,reporter,status,summary,created,issuetype,updated,assignee"New value: +"assignee,created,description,issuetype,labels,priority,reporter,status,summary,updated,versions"
    • addedInput schema / properties / use_display_names
      Added value: +{
+  "default": false,
+  "description": "When true, custom field keys in the output use human-readable display names (e.g. 'Story Points') instead of opaque IDs (e.g. 'customfield_10243'). The 'names' expansion is added automatically. Standard fields are unaffected.",
+  "type": "boolean"
+}
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. Changed1 schema field changedv1.2.1
    • changedInput schema / properties / fields / default
      Previous value: -"reporter,status,priority,created,issuetype,summary,updated,labels,description,assignee"New value: +"labels,versions,priority,description,reporter,status,summary,created,issuetype,updated,assignee"
  3. Changed1 schema field changed
    • changedInput schema / properties / fields / default
      Previous value: -"summary,issuetype,description,status,updated,created,reporter,labels,assignee,priority"New value: +"reporter,status,priority,created,issuetype,summary,updated,labels,description,assignee"
  4. Addedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds nothing further — no mention of result caps (limit max 50), pagination semantics differences between Cloud and Server, or project-visibility filtering constraints that would materially affect how an agent plans queries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero waste, which is structurally sound. But for an 8-parameter, open-world search tool it is under-specified rather than concise — brevity here comes at the cost of routing and behavioral information.

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?

An output schema exists, so return values needn't be described, and the input schema is fully documented. Still, a search tool with pagination, a project filter override, and a display-name toggle warrants at least a note on paging or scope, which the description omits.

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%, including rich JQL examples and per-field documentation, so the schema carries the full burden and baseline 3 applies. The description itself contributes no parameter meaning beyond restating the JQL acronym.

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 (Search) and resource (Jira issues) plus the query mechanism (JQL), so an agent knows exactly what it does. However, it does not distinguish itself from close siblings like jira_get_project_issues or jira_search_fields, which also return issue sets.

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

Usage Guidelines2/5

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

There is no guidance on when to reach for JQL search versus simpler siblings such as jira_get_project_issues, jira_get_board_issues, or jira_search_fields, and no exclusions or prerequisites. The agent must infer from the name alone that this is the general-purpose escape hatch.

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