Skip to main content
Glama
jerrelblankenship

Kibana MCP Server

list_dashboards

Retrieve Kibana dashboards with search filtering and pagination to find specific visualizations or monitor data displays.

Instructions

List all Kibana dashboards with optional search filtering

Input Schema

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

Implementation Reference

  • The handler logic for the 'list_dashboards' tool, which calls the Kibana client to fetch dashboard data and format it for the MCP response.
    case 'list_dashboards': {
      const { search, page = 1, perPage = 20 } = args || {};
      const result = await kibanaClient.listDashboards(
        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,
                dashboards: result.saved_objects.map((d) => ({
                  id: d.id,
                  title: d.attributes.title,
                  description: d.attributes.description,
                  updated_at: d.updated_at,
                })),
              },
              null,
              2
            ),
          },
        ],
      };
  • The registration of the 'list_dashboards' tool, including its schema, description, and available arguments.
    {
      name: 'list_dashboards',
      description:
        'List all Kibana dashboards with optional search filtering',
      inputSchema: {
        type: 'object',
        properties: {
          search: {
            type: 'string',
            description: 'Optional search term to filter dashboards 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?

No annotations are provided, so the description carries full burden. It mentions 'optional search filtering' but doesn't disclose important behavioral traits like whether this is a read-only operation, what permissions are needed, whether results are paginated (implied by parameters but not stated), or what the return format looks like. The description is minimal and lacks behavioral context.

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 waste. It's appropriately sized and front-loaded with the core purpose, making it easy to parse quickly.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a tool with 3 parameters and list functionality. It doesn't explain what the tool returns (dashboard objects, IDs, metadata?), doesn't mention authentication or rate limits, and provides minimal behavioral context. For a list tool with zero structured coverage, this is inadequate.

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?

Schema description coverage is 100%, so the schema already fully documents all three parameters. The description adds no additional parameter semantics beyond what's in the schema (e.g., doesn't explain search syntax or pagination behavior). Baseline 3 is appropriate when schema does all the work.

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 action ('List all Kibana dashboards') and resource ('Kibana dashboards'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_dashboard' or 'list_visualizations', which prevents a perfect score.

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

Usage Guidelines3/5

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

The description implies usage context through 'optional search filtering' but doesn't explicitly state when to use this tool versus alternatives like 'get_dashboard' (for single dashboard details) or 'search_logs' (for different resource types). No explicit when-not or alternative guidance is provided.

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