> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getmcpulse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Insights

> What is wrong, as sentences with a tool name, a number and a consequence: low first-call success, heavy payloads, silent empties, dead tools, slow tools.

With `clients` set, the same five rules run against one model's calls — so "low first-call on search_orders" stops being a server-wide average and becomes a statement about the model that is actually struggling with the description.



## OpenAPI

````yaml https://api.getmcpulse.com/docs/openapi.json get /v1/mcps/{id}/insights
openapi: 3.1.0
info:
  title: MCPulse API
  version: 1.0.0
  description: >-
    Analytics for MCP servers.


    The API is the product — the dashboard is one client and an MCP server will
    be another. Every number here is computed server-side so that both get the
    same answer.


    **Two kinds of auth.** Ingest uses an MCP API key (`mp_live_…`). Everything
    else uses a Supabase access token from the browser session.
servers:
  - url: https://mcpulse-production.up.railway.app
    description: MCPulse API
security: []
tags:
  - name: ingest
    description: What the customer's server sends
  - name: mcps
    description: MCPs and ownership
  - name: metrics
    description: Everything the dashboard reads
  - name: keys
    description: Ingest API keys
  - name: account
    description: Account, team and usage
paths:
  /v1/mcps/{id}/insights:
    get:
      tags:
        - metrics
      summary: Get Insights
      description: >-
        What is wrong, as sentences with a tool name, a number and a
        consequence: low first-call success, heavy payloads, silent empties,
        dead tools, slow tools.


        With `clients` set, the same five rules run against one model's calls —
        so "low first-call on search_orders" stops being a server-wide average
        and becomes a statement about the model that is actually struggling with
        the description.
      parameters:
        - schema:
            type: string
            format: uuid
          required: true
          name: id
          in: path
        - schema:
            type: string
            pattern: ^\d{4}-\d{2}-\d{2}$
          required: false
          name: from
          in: query
        - schema:
            type: string
            pattern: ^\d{4}-\d{2}-\d{2}$
          required: false
          name: to
          in: query
        - schema:
            type: string
            description: Comma-separated tool names. Omit for every tool.
          required: false
          description: Comma-separated tool names. Omit for every tool.
          name: tools
          in: query
        - schema:
            type: string
            description: Comma-separated client names. Omit for every client.
          required: false
          description: Comma-separated client names. Omit for every client.
          name: clients
          in: query
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                nullable: true
        '401':
          description: Invalid or missing token
        '404':
          description: Not found, or not yours

````