fix: Standardize MCP tool names and remove redundant search

Rename MCP tools for brevity and consistency.

Remove redundant jira_search_issues tool (use jira_ls_issues).

Author: aashari

README.md

@@ -106,7 +106,7 @@ This configuration launches the server automatically at runtime.
 
 This section covers the MCP tools available when using this server with an AI assistant. Note that MCP tools use `snake_case` for tool names and `camelCase` for parameters.
 
-## `jira_list_projects`
+## `jira_ls_projects`
 
 List available Jira projects with optional filtering and pagination.
 
@@ -142,7 +142,7 @@ _or:_
 
 ---
 
-## `jira_list_issues`
+## `jira_ls_issues`
 
 List issues matching a JQL (Jira Query Language) query with pagination.
 
@@ -178,24 +178,6 @@ _or:_
 
 ---
 
-## `jira_search_issues`
-
-Search Jira content using JQL (Jira Query Language) for advanced filtering.
-
-```json
-{ "jql": "text ~ 'login issue'" }
-```
-
-_or:_
-
-```json
-{ "jql": "project = PROJ AND priority = High AND created >= startOfMonth()" }
-```
-
-> "Search for high priority issues created this month in the PROJ project."
-
----
-
 # Command-Line Interface (CLI)
 
 The CLI uses kebab-case for commands (e.g., `jira-list-projects`) and options (e.g., `--project-key-or-id`).
@@ -232,7 +214,6 @@ Or get detailed help for a specific command:
 ```bash
 mcp-atlassian-jira jira-get-project --help
 mcp-atlassian-jira jira-list-issues --help
-mcp-atlassian-jira jira-search-issues --help
 ```
 
 ---

src/index.ts

@@ -11,7 +11,6 @@ import { runCli } from './cli/index.js';
 // Import Jira-specific tools
 import atlassianProjectsTools from './tools/atlassian.projects.tool.js';
 import atlassianIssuesTools from './tools/atlassian.issues.tool.js';
-import atlassianSearchTools from './tools/atlassian.search.tool.js';
 
 // Create a contextualized logger for this file
 const indexLogger = Logger.forContext('index.ts');
@@ -71,9 +70,6 @@ export async function startServer(mode: 'stdio' | 'sse' = 'stdio') {
 	atlassianIssuesTools.registerTools(serverInstance);
 	serverLogger.debug('Registered Issues tools');
 
-	atlassianSearchTools.registerTools(serverInstance);
-	serverLogger.debug('Registered Search tools');
-
 	serverLogger.info('All tools registered successfully');
 
 	try {

src/tools/atlassian.issues.tool.ts

@@ -116,7 +116,7 @@ function registerTools(server: McpServer) {
 
 	// Register the list issues tool
 	server.tool(
-		'jira_list_issues',
+		'jira_ls_issues',
 		`Searches for Jira issues using a JQL query (\`jql\`),\n\twith pagination support (\`limit\`, \`cursor\`).\n\n- Use this to find issues matching specific criteria (project, status, assignee, text, etc.).\n- Provides issue keys/IDs needed for \`jira_get_issue\`.\nReturns a formatted list of matching issues including key, summary, type, status, priority, project, and dates.\n**Note:** Requires valid JQL syntax. See Jira documentation for JQL details. Default sort is by last updated.`,
 		ListIssuesToolArgs.shape,
 		listIssues,

src/tools/atlassian.projects.tool.ts

@@ -117,7 +117,7 @@ function registerTools(server: McpServer) {
 
 	// Register the list projects tool
 	server.tool(
-		'jira_list_projects',
+		'jira_ls_projects',
 		`Lists Jira projects accessible to the user, optionally filtering by name/key (\`name\`) or sorting (\`orderBy\`).\n- Use this to discover available projects and find project keys/IDs needed for other tools (like \`jira_get_project\` or \`jira_list_issues\`).\n- Supports pagination via \`limit\` and \`cursor\`.\nReturns a formatted list of projects including key, name, type, style, lead, and URL.\n**Note:** Default sort is by most recently updated issue time.`,
 		ListProjectsToolArgs.shape,
 		listProjects,