MCP tools

issue_search read

Search issue titles and descriptions for a phrase. The query is matched as a phrase, so an operator or a wildcard in it is searched for literally rather than interpreted; a title holding one still finds its issue. Paginates like issue_list: limit up to 200, next_cursor back as cursor while has_more is true.

Arguments

NameTypeDescription
cursorstringthe next_cursor or prev_cursor from a previous call. The cursor knows which way it points, so one argument pages both ways
limitintegerhow many to return; 50 by default and 200 at most
query requiredstringfree text matched against issue titles and descriptions

Input schema

Exactly what tools/list serves.

input schema
{
  "additionalproperties": false,
  "properties": {
    "cursor": {
      "description": "the next_cursor or prev_cursor from a previous call. The cursor knows which way it points, so one argument pages both ways",
      "type": "string"
    },
    "limit": {
      "description": "how many to return; 50 by default and 200 at most",
      "type": "integer"
    },
    "query": {
      "description": "free text matched against issue titles and descriptions",
      "type": "string"
    }
  },
  "required": [
    "query"
  ],
  "type": "object"
}