Skip to main content
Glama
mshegolev

mshegolev/kibana-mcp

kibana_list_dashboards

Read-onlyIdempotent

List Kibana saved dashboards to discover available dashboard IDs with optional text search and pagination.

Instructions

List Kibana saved dashboards.

Calls GET {KIBANA_URL}/api/saved_objects/_find?type=dashboard. The kbn-xsrf: true header is always sent to satisfy Kibana's CSRF guard. Use this to discover dashboard IDs before calling kibana_get_dashboard.

Pagination: if has_more is True, call again with page + 1.

Examples: - Use when: "What Kibana dashboards are available?" → default params. - Use when: "Find the infrastructure dashboard." → search='infrastructure'. - Use when: "List all dashboards — page 2." → page=2. - Don't use when: You already have a dashboard ID — use kibana_get_dashboard directly (one fewer round trip). - Don't use when: You need log content — dashboards contain visualisation config, not raw log data. Use kibana_search_logs.

Returns: dict with total / page / page_size / has_more / dashboards (list of {id, title, description, updated_at}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoOptional text search in dashboard titles (case-insensitive substring match).
pageNoPage number (1-based).
page_sizeNoItems per page (1-100, default 20).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYes
pageYes
page_sizeYes
has_moreYes
searchYes
dashboardsYes
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds valuable context: the kbn-xsrf header requirement, pagination details (has_more, page+1), and return format. No contradictions.

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?

Description is well-structured with clear sections (endpoint, header, pagination, examples, return format). Every sentence adds value and it is appropriately sized.

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

Completeness5/5

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

Given the tool's simplicity, annotations, and output schema presence, the description covers all necessary aspects: pagination, search filtering, when to use, and return format. Complete.

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?

Input schema has 100% description coverage, so the description adds minimal value beyond schema. It provides example usage for search and page parameters, meeting the baseline for high coverage.

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

Purpose5/5

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

Description explicitly states 'List Kibana saved dashboards' and provides the HTTP endpoint. Examples distinguish this from sibling tools like kibana_get_dashboard and kibana_search_logs, making the purpose extremely clear.

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

Usage Guidelines5/5

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

The description includes explicit 'Use when' and 'Don't use when' examples, referencing sibling tools by name and explaining exactly when to choose this tool versus alternatives.

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/mshegolev/kibana-mcp'

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