Skip to main content
Glama
jerrelblankenship

Kibana MCP Server

get_visualization

Retrieve detailed information about a specific Kibana visualization using its unique ID to analyze data insights and dashboard components.

Instructions

Get detailed information about a specific visualization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVisualization ID

Implementation Reference

  • The handler for 'get_visualization' tool which calls the kibanaClient.getVisualization method.
    case 'get_visualization': {
      const { id } = args as { id: string };
      const visualization = await kibanaClient.getVisualization(id);
    
      return {
        content: [
          {
            type: 'text' as const,
            text: JSON.stringify(visualization, null, 2),
          },
        ],
      };
    }
  • KibanaClient method that performs the actual API request to retrieve a visualization.
     * Get a specific visualization by ID
     */
    async getVisualization(id: string): Promise<KibanaVisualization> {
      const response = await this.axiosInstance.get(
        `/api/saved_objects/visualization/${id}`
      );
      return response.data;
    }
  • Registration of the 'get_visualization' tool schema.
    {
      name: 'get_visualization',
      description: 'Get detailed information about a specific visualization',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'Visualization ID',
          },
        },
        required: ['id'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'get' operation which implies read-only behavior, but doesn't specify authentication requirements, rate limits, error conditions, or what format the 'detailed information' returns. The description adds minimal behavioral context beyond the basic operation type.

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

Conciseness4/5

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

The description is a single, efficient sentence that gets straight to the point without unnecessary words. It's appropriately sized for a simple retrieval tool, though it could potentially be more specific about what 'detailed information' includes to be more helpful.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what information is returned, error handling, authentication needs, or how this tool fits into the broader visualization/dashboard ecosystem with its siblings. The description leaves too many behavioral questions unanswered.

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 schema has 100% description coverage with the single parameter 'id' clearly documented as 'Visualization ID'. The description doesn't add any parameter semantics beyond what the schema already provides, but with complete schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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

Purpose3/5

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

The description states the tool 'Get detailed information about a specific visualization' clearly indicates a retrieval operation with a specific target, but it's somewhat vague about what 'detailed information' entails. It distinguishes from list_visualizations by focusing on a single item, but doesn't explicitly contrast with get_dashboard or other siblings beyond the resource type.

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?

No guidance is provided on when to use this tool versus alternatives. While it's implied this is for retrieving a single visualization when you have its ID, there's no mention of when to choose this over list_visualizations or how it relates to get_dashboard, export_dashboard, or other sibling tools.

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