Toolbox

Showing 25 of 41 from the live probe.

• Add Dashboard Element

  This tool creates a new tile (element) within an existing Looker dashboard. Tiles are added in the order this tool is called for a given `dashboard_id`. CRITICAL ORDER OF OPERATIONS: 1. Create the dashboard using `make_dashboard`. 2. Add any dashboard-level filters using `add_dashboard_filter`. 3. Then, add elements (tiles) using this tool. Required Parameters: - dashboard_id: The ID of the target dashboard, obtained from `make_dashboard`. - model_name, explore_name, fields: These query parame

• Add Dashboard Filter

  This tool adds a filter to a Looker dashboard. CRITICAL ORDER OF OPERATIONS: 1. Create a dashboard using `make_dashboard`. 2. Add all desired filters using this tool (`add_dashboard_filter`). 3. Finally, add dashboard elements (tiles) using `add_dashboard_element`. Parameters: - dashboard_id (required): The ID from `make_dashboard`. - name (required): A unique internal identifier for the filter. You will use this `name` later in `add_dashboard_element` to bind tiles to this filter. - title (re

• Create Project Directory

  This tool creates a new directory within a specified LookML project. Prerequisite: The Looker session must be in Development Mode. Use `dev_mode: true` first. Parameters: - project_id (required): The unique ID of the LookML project. - directory_path (required): The path to the new directory within the project. Output: A confirmation message upon successful directory creation.

• Create Project File

  This tool creates a new LookML file within a specified project, populating it with the provided content. Prerequisite: The Looker session must be in Development Mode. Use `dev_mode: true` first. Parameters: - project_id (required): The unique ID of the LookML project. - file_path (required): The desired path and filename for the new file within the project. - content (required): The full LookML content to write into the new file. Output: A confirmation message upon successful file creation.

• Create View From Table

  This tool generates boilerplate LookML views directly from the database schema. It does not create model or explore files, only view files in the specified folder. Prerequisite: The Looker session must be in Development Mode. Use `dev_mode: true` first. Parameters: - project_id (required): The unique ID of the LookML project. - connection (required): The database connection name. - tables (required): A list of objects to generate views for. Each object must contain `schema` and `table_name` (n

• Delete Project Directory

  This tool permanently deletes a specified directory within a LookML project. Prerequisite: The Looker session must be in Development Mode. Use `dev_mode: true` first. Parameters: - project_id (required): The unique ID of the LookML project. - directory_path (required): The path to the directory within the project. Output: A confirmation message upon successful directory deletion.

• Delete Project File

  This tool permanently deletes a specified LookML file from within a project. Use with caution, as this action cannot be undone through the API. Prerequisite: The Looker session must be in Development Mode. Use `dev_mode: true` first. Parameters: - project_id (required): The unique ID of the LookML project. - file_path (required): The exact path to the LookML file to delete within the project. Output: A confirmation message upon successful file deletion.

• Dev Mode

  This tool allows toggling the Looker IDE session between Development Mode and Production Mode. Development Mode enables making and testing changes to LookML projects. Parameters: - enable (required): A boolean value. - `true`: Switches the current session to Development Mode. - `false`: Switches the current session to Production Mode.

• Generate Embed Url

  This tool generates a signed, private embed URL for specific Looker content, allowing users to access it directly. Parameters: - type (required): The type of content to embed. Common values include: - `dashboards` - `looks` - `explore` - id (required): The unique identifier for the content. - For dashboards and looks, use the numeric ID (e.g., "123"). - For explores, use the format "model_name/explore_name".

• Get Connection Databases

  This tool retrieves a list of databases available through a specified Looker connection. This is only applicable for connections that support multiple databases. Use `get_connections` to check if a connection supports multiple databases. Parameters: - connection_name (required): The name of the database connection, obtained from `get_connections`. Output: A JSON array of strings, where each string is the name of an available database. If the connection does not support multiple databases, an e

• Get Connection Schemas

  This tool retrieves a list of database schemas available through a specified Looker connection. Parameters: - connection_name (required): The name of the database connection, obtained from `get_connections`. - database (optional): An optional database name to filter the schemas. Only applicable for connections that support multiple databases. Output: A JSON array of strings, where each string is the name of an available schema.

• Get Connection Table Columns

  This tool retrieves a list of columns for one or more specified tables within a given database schema and connection. Parameters: - connection_name (required): The name of the database connection, obtained from `get_connections`. - schema (required): The name of the schema where the tables reside, obtained from `get_connection_schemas`. - tables (required): A comma-separated string of table names for which to retrieve columns (e.g., "users,orders,products"), obtained from `get_connection_tabl

• Get Connection Tables

  This tool retrieves a list of tables available within a specified database schema through a Looker connection. Parameters: - connection_name (required): The name of the database connection, obtained from `get_connections`. - schema (required): The name of the schema to list tables from, obtained from `get_connection_schemas`. - database (optional): The name of the database to filter by. Only applicable for connections that support multiple databases (check with `get_connections`). Output: A

• Get Connections

  This tool retrieves a list of all database connections configured in the Looker system. Parameters: This tool takes no parameters. Output: A JSON array of objects, each representing a database connection and including details such as: - `name`: The connection's unique identifier. - `dialect`: The database dialect (e.g., "mysql", "postgresql", "bigquery"). - `default_schema`: The default schema for the connection. - `database`: The associated database name (if applicable). - `supports_multiple_

• Get Dashboards

  This tool searches for saved dashboards in a Looker instance. It returns a list of JSON objects, each representing a dashboard. Search Parameters: - title (optional): Filter by dashboard title (supports wildcards). - folder_id (optional): Filter by the ID of the folder where the dashboard is saved. - user_id (optional): Filter by the ID of the user who created the dashboard. - description (optional): Filter by description content (supports wildcards). - id (optional): Filter by specific dashboa

• Get Dimensions

  This tool retrieves a list of dimensions defined within a specific Looker explore. Dimensions are non-aggregatable attributes or characteristics of your data (e.g., product name, order date, customer city) that can be used for grouping, filtering, or segmenting query results. Parameters: - model_name (required): The name of the LookML model, obtained from `get_models`. - explore_name (required): The name of the explore within the model, obtained from `get_explores`. Output Details: - If a dime

• Get Explores

  This tool retrieves a list of explores defined within a specific LookML model. Explores represent a curated view of your data, typically joining several tables together to allow for focused analysis on a particular subject area. The output provides details like the explore's `name` and `label`. Parameters: - model_name (required): The name of the LookML model, obtained from `get_models`.

• Get Field Value Suggestions

  This tool retrieves distinct value suggestions for a field, facilitating accurate filtering in downstream queries. Required Parameters: - model: The name of the LookML model, obtained from `get_models`. - explore: The name of the explore containing the field, obtained from `get_explores`. - field: The name of the field to get suggestions for (obtained from a dimension where 'suggestable' is true in the 'get_dimensions' output). Optional Parameters: - term: Optional search term pattern to filte

• Get Filters

  This tool retrieves a list of "filter-only fields" defined within a specific Looker explore. These are special fields defined in LookML specifically to create user-facing filter controls that do not directly affect the `GROUP BY` clause of the SQL query. They are often used in conjunction with liquid templating to create dynamic queries. Note: Regular dimensions and measures can also be used as filters in a query. This tool *only* returns fields explicitly defined as `filter:` in LookML. Param

• Get Lookml Tests

  Returns a list of tests which can be run to validate a project's LookML code and/or the underlying data, optionally filtered by the file id. Prerequisite: The Looker session must be in Development Mode. Use `dev_mode: true` first. Parameters: - project_id (required): The unique ID of the LookML project. - file_id (optional): The ID of the file to filter tests by. This must be the complete file path from the project root (e.g., `models/my_model.model.lkml` or `views/my_view.view.lkml`). Output

• Get Looks

  This tool searches for saved Looks (pre-defined queries and visualizations) in a Looker instance. It returns a list of JSON objects, each representing a Look. Search Parameters: - title (optional): Filter by Look title (supports wildcards). - folder_id (optional): Filter by the ID of the folder where the Look is saved. - user_id (optional): Filter by the ID of the user who created the Look. - description (optional): Filter by description content (supports wildcards). - id (optional): Filter by

• Get Measures

  This tool retrieves a list of measures defined within a specific Looker explore. Measures are aggregatable metrics (e.g., total sales, average price, count of users) that are used for calculations and quantitative analysis in your queries. Parameters: - model_name (required): The name of the LookML model, obtained from `get_models`. - explore_name (required): The name of the explore within the model, obtained from `get_explores`. Output Details: - If a measure includes a `suggestions` field, i

• Get Models

  This tool retrieves a list of available LookML models in the Looker instance. LookML models define the data structure and relationships that users can query. The output includes details like the model's `name` and `label`, which are essential for subsequent calls to tools like `get_explores` or `query`. This tool takes no parameters.

• Get Parameters

  This tool retrieves a list of parameters defined within a specific Looker explore. LookML parameters are dynamic input fields that allow users to influence query behavior without directly modifying the underlying LookML. They are often used with `liquid` templating to create flexible dashboards and reports, enabling users to choose dimensions, measures, or other query components at runtime. Parameters: - model_name (required): The name of the LookML model, obtained from `get_models`. - explore_

• Get Project Directories

  This tool retrieves the list of directories within a specified LookML project. Parameters: - project_id (required): The unique ID of the LookML project. Output: A JSON array of strings, where each string is the name of a directory within the project.