refactor(atlassian/jira): standardize list to search terminology

Replace all 'list' naming with 'search' across Jira commands to provide
consistent terminology reflecting the actual JQL search functionality.

Changes:
- Rename module: list.rs → search.rs
- Rename struct: ListOptions → SearchOptions
- Rename struct: ListOutput → SearchOutput
- Rename function: list_issues_data() → search_issues_data()
- Update CLI command: 'jira list' → 'jira search'
- Update all help examples and documentation
- Update MCP tool handler variable names

The MCP tool name 'jira_search' was already correct and remains unchanged.

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

Author: guzmonne

crates/core/src/atlassian/jira.rs

@@ -67,9 +67,9 @@ pub struct IssueOutput {
     pub assignee: Option<String>,
 }
 
-/// Output structure for list command
+/// Output structure for search command
 #[derive(Debug, Serialize, PartialEq)]
-pub struct ListOutput {
+pub struct SearchOutput {
     pub issues: Vec<IssueOutput>,
     pub total: usize,
     #[serde(skip_serializing_if = "Option::is_none")]
@@ -350,8 +350,8 @@ fn render_adf_node(node: &serde_json::Value, depth: usize) -> Option<String> {
 /// * `search_response` - The raw response from Jira search API
 ///
 /// # Returns
-/// * `ListOutput` - Cleaned and transformed search results
-pub fn transform_search_response(search_response: JiraSearchResponse) -> ListOutput {
+/// * `SearchOutput` - Cleaned and transformed search results
+pub fn transform_search_response(search_response: JiraSearchResponse) -> SearchOutput {
     let issues: Vec<IssueOutput> = search_response
         .issues
         .into_iter()
@@ -375,7 +375,7 @@ pub fn transform_search_response(search_response: JiraSearchResponse) -> ListOut
     // GET /rest/api/3/search/jql always returns 'total' field
     let total = search_response.total.map(|t| t as usize).unwrap_or(0);
 
-    ListOutput {
+    SearchOutput {
         issues,
         total,
         next_page_token: search_response.next_page_token,

crates/mcptools/src/atlassian/jira/mod.rs

@@ -1,5 +1,5 @@
 pub mod get;
-pub mod list;
+pub mod search;
 
 use crate::prelude::{println, *};
 
@@ -8,7 +8,7 @@ use crate::prelude::{println, *};
 pub enum Commands {
     /// Search Jira issues using JQL
     #[clap(name = "search")]
-    Search(list::ListOptions),
+    Search(search::SearchOptions),
 
     /// Get detailed information about a Jira ticket
     #[clap(name = "get")]
@@ -22,11 +22,11 @@ pub async fn run(cmd: Commands, global: crate::Global) -> Result<()> {
     }
 
     match cmd {
-        Commands::Search(options) => list::handler(options).await,
+        Commands::Search(options) => search::handler(options).await,
         Commands::Get(options) => get::handler(options).await,
     }
 }
 
 // Re-export public data functions for external use (e.g., MCP)
 pub use get::get_ticket_data;
-pub use list::list_issues_data;
+pub use search::search_issues_data;

…ates/mcptools/src/atlassian/jira/list.rs …es/mcptools/src/atlassian/jira/search.rscrates/mcptools/src/atlassian/jira/list.rs renamed to crates/mcptools/src/atlassian/jira/search.rs crates/mcptools/src/atlassian/jira/list.rs renamed to crates/mcptools/src/atlassian/jira/search.rs

@@ -3,28 +3,28 @@ use serde::{Deserialize, Serialize};
 
 // Import domain models and pure functions from core crate
 use mcptools_core::atlassian::jira::transform_search_response;
-pub use mcptools_core::atlassian::jira::{IssueOutput, JiraSearchResponse, ListOutput};
+pub use mcptools_core::atlassian::jira::{IssueOutput, JiraSearchResponse, SearchOutput};
 
-/// Options for listing Jira issues
+/// Options for searching Jira issues
 #[derive(Debug, clap::Args, Serialize, Deserialize, Clone)]
 #[command(after_help = "EXAMPLES:
   # Get all tickets assigned to the current user:
-  mcptools atlassian jira list \"assignee = currentUser()\"
+  mcptools atlassian jira search \"assignee = currentUser()\"
 
   # Get only active tickets (excluding Done/Closed):
-  mcptools atlassian jira list \"assignee = currentUser() AND status NOT IN (Done, Closed)\"
+  mcptools atlassian jira search \"assignee = currentUser() AND status NOT IN (Done, Closed)\"
 
   # Get only completed tickets (Done/Closed):
-  mcptools atlassian jira list \"assignee = currentUser() AND status IN (Done, Closed)\"
+  mcptools atlassian jira search \"assignee = currentUser() AND status IN (Done, Closed)\"
 
   # Find tickets by summary (search by name):
-  mcptools atlassian jira list \"summary ~ \\\"bug fix\\\"\"
+  mcptools atlassian jira search \"summary ~ \\\"bug fix\\\"\"
 
   # Combine criteria: active tickets with specific text in summary:
-  mcptools atlassian jira list \"assignee = currentUser() AND status NOT IN (Done, Closed) AND summary ~ \\\"api\\\"\"
+  mcptools atlassian jira search \"assignee = currentUser() AND status NOT IN (Done, Closed) AND summary ~ \\\"api\\\"\"
 
   # Fetch next page using pagination token:
-  mcptools atlassian jira list \"assignee = currentUser()\" --limit 50 --next-page <token>
+  mcptools atlassian jira search \"assignee = currentUser()\" --limit 50 --next-page <token>
 
 NOTES:
   - JQL queries use Jira Query Language syntax
@@ -34,7 +34,7 @@ NOTES:
   - Results are limited to 10 per page by default; use --limit to change
   - Use --next-page with the token from the previous response to fetch additional pages
   - Pagination tokens expire after 7 days")]
-pub struct ListOptions {
+pub struct SearchOptions {
     /// JQL query (e.g., "project = PROJ AND status = Open")
     #[clap(env = "JIRA_QUERY")]
     pub query: String,
@@ -55,11 +55,11 @@ pub struct ListOptions {
 /// Public data function - used by both CLI and MCP
 /// Supports pagination with nextPageToken using GET /rest/api/3/search/jql
 /// Note: This endpoint uses token-based pagination, not offset-based
-pub async fn list_issues_data(
+pub async fn search_issues_data(
     query: String,
     limit: usize,
     next_page: Option<String>,
-) -> Result<ListOutput> {
+) -> Result<SearchOutput> {
     use crate::atlassian::{create_authenticated_client, AtlassianConfig};
 
     let config = AtlassianConfig::from_env()?;
@@ -113,9 +113,9 @@ pub async fn list_issues_data(
     Ok(transform_search_response(search_response))
 }
 
-/// Handle the list command
-pub async fn handler(options: ListOptions) -> Result<()> {
-    let data = list_issues_data(options.query.clone(), options.limit, options.next_page).await?;
+/// Handle the search command
+pub async fn handler(options: SearchOptions) -> Result<()> {
+    let data = search_issues_data(options.query.clone(), options.limit, options.next_page).await?;
 
     if options.json {
         println!("{}", serde_json::to_string_pretty(&data)?);
@@ -149,7 +149,7 @@ pub async fn handler(options: ListOptions) -> Result<()> {
 
         // Print pagination info
         if let Some(next_token) = &data.next_page_token {
-            eprintln!("\nTo fetch the next page, run:\n  mcptools atlassian jira list '{}' --limit {} --next-page {}",
+            eprintln!("\nTo fetch the next page, run:\n  mcptools atlassian jira search '{}' --limit {} --next-page {}",
                 options.query, options.limit, next_token);
         }
     }

crates/mcptools/src/main.rs

@@ -29,7 +29,7 @@ pub struct App {
 #[derive(Debug, Clone, clap::Args)]
 pub struct Global {
     /// Whether to display additional information.
-    #[clap(long, env = "YAWNS_VERBOSE", global = true, default_value = "false")]
+    #[clap(long, env = "MCPTOOLS_VERBOSE", global = true, default_value = "false")]
     verbose: bool,
 
     /// Atlassian base URL (e.g., https://your-domain.atlassian.net)

crates/mcptools/src/mcp/tools/atlassian.rs

@@ -9,19 +9,19 @@ pub async fn handle_jira_search(
     global: &crate::Global,
 ) -> Result<serde_json::Value, JsonRpcError> {
     #[derive(Deserialize)]
-    struct JiraListArgs {
+    struct JiraSearchArgs {
         query: String,
         limit: Option<usize>,
         #[serde(rename = "nextPageToken")]
         next_page_token: Option<String>,
     }
 
-    let args: JiraListArgs = serde_json::from_value(arguments.unwrap_or(serde_json::Value::Null))
+    let args: JiraSearchArgs = serde_json::from_value(arguments.unwrap_or(serde_json::Value::Null))
         .map_err(|e| JsonRpcError {
-        code: -32602,
-        message: format!("Invalid arguments: {e}"),
-        data: None,
-    })?;
+            code: -32602,
+            message: format!("Invalid arguments: {e}"),
+            data: None,
+        })?;
 
     if global.verbose {
         eprintln!(
@@ -35,7 +35,7 @@ pub async fn handle_jira_search(
     }
 
     // Call the Jira module's data function
-    let list_data = crate::atlassian::jira::list_issues_data(
+    let search_data = crate::atlassian::jira::search_issues_data(
         args.query,
         args.limit.unwrap_or(10),
         args.next_page_token,
@@ -48,7 +48,7 @@ pub async fn handle_jira_search(
     })?;
 
     // Convert to JSON and wrap in MCP result format
-    let json_string = serde_json::to_string_pretty(&list_data).map_err(|e| JsonRpcError {
+    let json_string = serde_json::to_string_pretty(&search_data).map_err(|e| JsonRpcError {
         code: -32603,
         message: format!("Serialization error: {e}"),
         data: None,

docs/ATLASSIAN_SETUP.md

@@ -87,7 +87,7 @@ Then load it before running commands:
 
 ```bash
 source .env
-mcptools atlassian jira list "project = PROJ"
+mcptools atlassian jira search "project = PROJ"
 ```
 
 ### Option D: Pass as Command-Line Arguments
@@ -97,15 +97,15 @@ mcptools \
   --atlassian-url "https://your-domain.atlassian.net" \
   --atlassian-email "your-email@company.com" \
   --atlassian-token "your-api-token-here" \
-  atlassian jira list "project = PROJ"
+  atlassian jira search "project = PROJ"
 ```
 
 ## Step 4: Verify Configuration
 
 Test your configuration with a simple Jira query:
 
 ```bash
-mcptools atlassian jira list "project IS NOT EMPTY" --limit 5
+mcptools atlassian jira search "project IS NOT EMPTY" --limit 5
 ```
 
 Expected output (if successful):
@@ -126,24 +126,24 @@ If you get an error like `ATLASSIAN_BASE_URL environment variable not set`, ensu
 
 ### Jira Commands
 
-**List open issues in a project:**
+**Search for open issues in a project:**
 ```bash
-mcptools atlassian jira list "project = PROJ AND status = Open"
+mcptools atlassian jira search "project = PROJ AND status = Open"
 ```
 
-**List issues assigned to you:**
+**Search for issues assigned to you:**
 ```bash
-mcptools atlassian jira list "assignee = currentUser()"
+mcptools atlassian jira search "assignee = currentUser()"
 ```
 
 **Search with JQL and limit results:**
 ```bash
-mcptools atlassian jira list "text ~ 'database' AND status = 'In Progress'" --limit 20
+mcptools atlassian jira search "text ~ 'database' AND status = 'In Progress'" --limit 20
 ```
 
 **Output as JSON:**
 ```bash
-mcptools atlassian jira list "project = PROJ" --json | jq '.issues[] | {key, summary, status}'
+mcptools atlassian jira search "project = PROJ" --json | jq '.issues[] | {key, summary, status}'
 ```
 
 ### Confluence Commands
@@ -167,7 +167,7 @@ mcptools atlassian confluence search "text ~ 'api'" --limit 5 --json
 
 The Atlassian module is also available as MCP tools that Claude can use:
 
-- **`jira_list`** - Search Jira issues using JQL
+- **`jira_search`** - Search Jira issues using JQL
 - **`confluence_search`** - Search Confluence pages using CQL
 
 These tools are automatically available when using mcptools as an MCP server.