Tool:list_parsers

List all parsers for a given log type, returning only metadata.

Retrieves a list of parser metadata for a specific log type, or for all log types if "-" is specified. This tool is useful for getting an overview of existing parsers and their states without fetching the full parser code.

Agent Responsibilities: - The response is a JSON object. The agent should access theparsers key to get a list of parser objects. - Each object in the list contains parser metadata such asname,log_type,state,create_time, etc. - Thename field contains the full resource name, from which the parser ID can be extracted. - If the response contains anext_page_token, it indicates that more results are available. The agent should use this token in a subsequent call to retrieve the next page. - The agent should not present the raw JSON. Instead, it should format the output as a human-readable list, for example, using a table or a bulleted list.

Workflow Integration: - Use to discover existing parsers for a specific log type. - Helpful for finding a parser ID to use with other tools likeget_parser oractivate_parser. - Use to audit which parsers exist for a customer and their current states (ACTIVE, INACTIVE, etc.).

Args: project_id (str): Google Cloud project ID (required). customer_id (str): Chronicle customer ID (required). region (str): Chronicle region (e.g., "us", "europe") (required). log_type (str): Chronicle log type identifier for the parser. Use "-" to list parsers for all log types. Defaults to "-". page_size (int): The maximum number of parsers to return. The service may return fewer than this value. page_token (str): A page token, received from a previouslist_parsers call. Provide this to retrieve the subsequent page. filter (str): A filter to be applied to the list of parsers.

Returns: str: Raw JSON response from the API, representing a list of Parser metadata objects. The agent should parse this and present a formatted list to the user. Returns an error message if listing fails.

Example Usage: # List all parsers for a specific log type list_parsers( project_id="my-project", customer_id="my-customer", region="us", log_type="OKTA" )

# List all parsers for all log types        list_parsers(            project_id="my-project",            customer_id="my-customer",            region="us"        )

The following sample demonstrate how to usecurl to invoke thelist_parsers MCP tool.

Input Schema

{"projectId":string,"customerId":string,"region":string,"logType":string,"pageSize":integer,"pageToken":string,"filter":string}

Output Schema

{"parsers":[{object (Parser)}],"nextPageToken":string}

{"projectId":string,"customerId":string,"region":string,"logType":string,"parserId":string,"state":enum (State),"createTime":string,"code":string}

{"seconds":string,"nanos":integer}

Tool Annotations

Destructive Hint: ❌ | Idempotent Hint: ❌ | Read Only Hint: ✅ | Open World Hint: ❌