Skip to main content
Glama
jerrelblankenship

Kibana MCP Server

list_visualizations

Retrieve and filter Kibana visualizations by title with pagination support for efficient data exploration.

Instructions

List all Kibana visualizations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoOptional search term to filter visualizations by title
pageNoPage number for pagination (default: 1)
perPageNoNumber of results per page (default: 20, max: 100)

Implementation Reference

  • Tool handler in src/tools/index.ts that parses arguments and calls the Kibana client to list visualizations.
    case 'list_visualizations': {
      const { search, page = 1, perPage = 20 } = args || {};
      const result = await kibanaClient.listVisualizations(
        search as string | undefined,
        page as number,
        Math.min(perPage as number, 100)
      );
    
      return {
        content: [
          {
            type: 'text' as const,
            text: JSON.stringify(
              {
                total: result.total,
                page,
                per_page: result.per_page,
                visualizations: result.saved_objects.map((v) => ({
                  id: v.id,
                  title: v.attributes.title,
                  description: v.attributes.description,
                  updated_at: v.updated_at,
                })),
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • The actual Kibana API client method that performs the request to list visualizations.
     * List all visualizations
     */
    async listVisualizations(
      search?: string,
      page = 1,
      perPage = 20
    ): Promise<SavedObjectsResponse<KibanaVisualization>> {
      const params: any = {
        type: 'visualization',
        per_page: perPage,
        page,
      };
    
      if (search) {
        params.search = search;
        params.search_fields = 'title';
      }
    
      const response = await this.axiosInstance.get('/api/saved_objects/_find', {
        params,
      });
    
      return response.data;
    }
  • Tool definition/registration for list_visualizations.
      name: 'list_visualizations',
      description: 'List all Kibana visualizations',
      inputSchema: {
        type: 'object',
        properties: {
          search: {
            type: 'string',
            description:
              'Optional search term to filter visualizations by title',
          },
          page: {
            type: 'number',
            description: 'Page number for pagination (default: 1)',
            default: 1,
          },
          perPage: {
            type: 'number',
            description:
              'Number of results per page (default: 20, max: 100)',
            default: 20,
          },
        },
      },
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('List') but doesn't mention whether this is a read-only operation, if it requires authentication, what the output format looks like, or any rate limits. For a listing tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a straightforward listing tool, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (a simple list operation) and the schema's full parameter coverage, the description is minimally adequate. However, without annotations or an output schema, it fails to explain what the returned data looks like (e.g., structure, fields) or any behavioral nuances, leaving room for improvement in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, clearly documenting all three parameters (search, page, perPage) with their types, defaults, and constraints. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline for adequate but not exceptional coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('all Kibana visualizations'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'get_visualization' (singular vs. plural), which suggests a potential overlap in functionality that isn't clarified.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'get_visualization' or 'list_dashboards'. It lacks any context about prerequisites, typical use cases, or exclusions, leaving the agent to infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jerrelblankenship/jb-kibana-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server