Tools Reference

Tools: Logs & Health

Observability tools let you read project logs, search for errors, run tests, and monitor system health.

zeeb_read_logs

Read recent log output from the project.

zeeb_read_logs(lines?: int, level?: str, project_id) → str

Arguments:

Name	Type	Description
`lines`	int?	Number of log lines to return (default: 100)
`level`	string?	Filter by log level: `DEBUG`, `INFO`, `WARNING`, `ERROR`, `CRITICAL`
`project_id`	string	UUID of the target project

Returns: Recent log lines with timestamps and levels.

Example prompt: "Show me the last 50 error logs from my project"

Search for a pattern in the project logs.

zeeb_search_logs(query: str, lines?: int, project_id) → str

Arguments:

Name	Type	Description
`query`	string	Text or regex pattern to search for
`lines`	int?	Max lines to return (default: 50)
`project_id`	string	UUID of the target project

Example prompt: "Find all 500 errors in the logs"

Run the project's test suite.

zeeb_run_tests(app?: str, test_path?: str, project_id) → str

Arguments:

Name	Type	Description
`app`	string?	Run only tests for this app
`test_path`	string?	Specific test file or class to run
`project_id`	string	UUID of the target project

Returns: Test results with pass/fail counts and tracebacks for failures.

Example prompt: "Run the tests for the blog app"

Add a /health liveness endpoint to the project.

zeeb_create_health_endpoint(project_id) → str

Creates a GET /health route that returns:

{
  "status": "ok",
  "timestamp": "2026-01-01T00:00:00Z",
  "version": "1.0.0"
}

This endpoint is required for production readiness (zeeb_check_production_readiness will flag if missing).

Check the health of the project's runtime (database connection, migrations, etc.).

zeeb_check_system_health(project_id) → str

Checks:

Check	Description
Database connection	Can the project connect to its database?
Pending migrations	Are there unapplied migrations?
App registry	Are all apps loading without errors?
Preview status	Is the preview environment running?

Read environment variables set for the project.

zeeb_get_env(project_id) → str

Returns: Current environment variable names (values may be masked for sensitive keys).

Set an environment variable for the project.

zeeb_set_env(key: str, value: str, project_id) → str

The project preview is restarted automatically after setting environment variables.

Delete an environment variable.

zeeb_delete_env(key: str, project_id) → str

Read the current Django/zeebpy settings for the project.

zeeb_get_settings(project_id) → str

Returns: Key settings values (DEBUG, INSTALLED_APPS, DATABASES, etc.).

Logs come from the live preview container — they reflect the running application.
zeeb_run_tests uses pytest under the hood.
Environment variables set via zeeb_set_env are persisted across preview restarts.