Atlassian MCP Server

jira_search_issues

Search Jira issues using JQL queries to locate specific tasks. Control results with pagination and max limits for efficient retrieval.

Instructions

Поиск задач Jira по JQL-запросу

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": {
      "jql": "<jql>"
    },
    "name": "jira_search_issues"
  }
}

Input Schema

Name	Required	Description
`jql`	Yes	JQL-запрос для поиска (например: 'project = PROJ AND status = "In Progress"')
`startAt`	No	Смещение для пагинации
`maxResults`	No	Максимальное количество результатов (по умолчанию 25)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the responsibility for behavioral context. 'Поиск' clearly implies a read-only operation and no side effects, which is useful. However, the description does not disclose output shape, pagination behavior, or any permissions or limitations beyond what the schema already shows.

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 a single, front-loaded sentence with no filler or redundant text. It conveys the essential purpose immediately and wastes no words.

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?

For a simple JQL search tool, the description plus the fully documented schema covers the core invocation needs. However, with no output schema and no annotations, the description does not mention what the response contains or that results are paginated, leaving some contextual gaps.

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%, with all three parameters (jql, startAt, maxResults) already documented with descriptions and defaults. The description adds no additional parameter semantics beyond the schema, which matches the baseline of 3.

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?

Description states a specific action ('Поиск задач Jira') and the exact mechanism ('по JQL-запросу'). This clearly distinguishes it from sibling tools like jira_get_issue, jira_create_issue, and jira_update_issue, which operate on individual issues rather than search.

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 JQL search mechanism implies the tool is for finding issues by query, but the description does not explicitly say when to use it over alternatives or when not to use it. The intended use is inferable from the phrase 'по JQL-запросу', so there is some guidance, but no explicit exclusion or sibling comparison.

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

Deploy Server