WHEN TO USE: To get a list of all brand monitoring projects for the current user. Use as the FIRST step to discover available projects before working with scans or results. RETURNS: Compact CSV with id, brand_name, status, visibility_pct, models_count, prompts_count (default). Set include_all_fields=true for full JSON. NEXT STEP: Use lbm_get_project with a specific project id for full details.

WHEN TO USE: To get full details of a specific brand monitoring project including all prompts. REQUIRES: project_id from lbm_list_projects. RETURNS: Project object with id, name, description, status, models, prompts array, schedule, and stats.

WHEN TO USE: To create a new brand monitoring project. RETURNS: Created project object with generated id. NEXT STEP: Call lbm_run_scan to start monitoring.

WHEN TO USE: To update project name, models, or auto monitoring settings. Only provided fields are updated. NOTE: brand_name and prompts cannot be modified via this endpoint. Use lbm_add_prompts/lbm_delete_prompt for prompt changes. REQUIRES: project_id from lbm_list_projects. RETURNS: Updated project object.

WHEN TO USE: To archive a project that is no longer needed. Archived projects are hidden but not deleted. REQUIRES: project_id from lbm_list_projects. Confirm with user before archiving.

WHEN TO USE: To add one or more monitoring prompts to a project. Prompts are the questions asked to LLMs (e.g. "What are the best tools for X?"). Max 50 per request, 100 per project total. REQUIRES: project_id from lbm_list_projects. RETURNS: Array of created prompts with prompt_id. NEXT STEP: Call lbm_run_scan to run a scan with the new prompts.

WHEN TO USE: To remove a specific prompt from a project. REQUIRES: project_id and prompt_id. Get prompt_id from lbm_get_project (prompts array). NOTE: Project must have at least 2 prompts; cannot delete from archived project. Confirm with user before deleting.

WHEN TO USE: To start a new monitoring scan for a project — sends prompts to all configured LLMs and collects responses. REQUIRES: project_id from lbm_list_projects. Project must have at least one prompt (use lbm_add_prompts if needed). RETURNS: Created scan object with scan_id and status="pending". NEXT STEP: Poll lbm_get_scan_status with scan_id until status="completed". CAUTION: This SPENDS user credits. Always confirm with the user before running.

WHEN TO USE: To check the status of a running or completed scan. REQUIRES: project_id and scan_id from lbm_run_scan or lbm_list_scans. RETURNS: Scan object with status (pending/running/completed/failed), progress, start/end times, and result count. NEXT STEP: When status="completed", call lbm_list_results to see monitoring results.

WHEN TO USE: To see the scan history for a project — all past and current scans with their statuses. REQUIRES: project_id from lbm_list_projects. RETURNS: Compact CSV with scan_id, status, created_at, results_count (default). Set include_all_fields=true for full JSON.

WHEN TO USE: To get monitoring results for a project — how LLMs responded to brand monitoring prompts. REQUIRES: project_id from lbm_list_projects. RETURNS: Compact CSV with result_id, prompt, model, brand_mentioned, status (default limit: 20). Set include_all_fields=true for full JSON. NEXT STEP: Use lbm_get_transcript with a result_id to read the full LLM response text.

WHEN TO USE: To read the full verbatim LLM response for a specific monitoring result. Use when the user wants to see exactly what an LLM said about their brand. REQUIRES: project_id and result_id from lbm_list_results. RETURNS: Full transcript text, model name, prompt text, and metadata (brand_mentioned, sentiment, links found).

WHEN TO USE: To see which competitor brands were mentioned by LLMs in responses to this project's prompts. Shows competitive landscape as seen by AI models. REQUIRES: project_id from lbm_list_projects. RETURNS: Compact CSV with competitor name, mention count, frequency % (default limit: 20). Set include_all_fields=true for full JSON. Pass higher limit only if user explicitly asks for more.

WHEN TO USE: To see which URLs and domains LLMs cited in their responses — useful for understanding what sources AI models trust for this topic. REQUIRES: project_id from lbm_list_projects. RETURNS: Compact CSV with domain, mentions, unique_urls (default limit: 20). Set include_all_fields=true for full JSON with individual URLs. Pass higher limit only if user explicitly asks for more.

WHEN TO USE: To see competitor mention trends over time — which competitors were mentioned by LLMs across multiple scans and how their visibility changed. Use for competitive trend analysis and reporting. REQUIRES: project_id from lbm_list_projects. RETURNS: Historical competitor mention statistics per date, with per-model breakdowns. NOTE: Response structure may differ between time_range and start_date/end_date params.

WHEN TO USE: To discover which LLM models are available for brand monitoring scans. Call this before creating a project or running a scan if the user wants to choose specific models. RETURNS: Compact CSV with model_id, name, provider, web_search (default). Set include_all_fields=true for full JSON with pricing.

WHEN TO USE: To check credit balance and usage statistics. Call this before lbm_run_scan to confirm the user has enough credits. RETURNS: Current credit balance, credits used this period, credits per scan estimate, and usage breakdown by model and project.