Skip to main content
Glama

posthog_list_insights

Read-onlyIdempotent

Retrieve saved PostHog insights (charts) for a project, with optional name filtering and result limits, to review analytics dashboards and saved reports.

Instructions

List saved PostHog insights (charts) for a project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "api_key": "<api_key>"
    },
    "name": "posthog_list_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoPostHog host (default https://us.posthog.com)
limitNoResults to return (max 100, default 25)
searchNoFilter insights by name
api_keyYesPostHog Personal API key
project_idNoPostHog project id (can be a saved default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds that results are 'saved' insights for a project, but says nothing about pagination/limit behavior or default ordering that an agent would want before calling.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity edges toward under-specification rather than optimal density.

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?

For a simple read-only list tool with a fully documented schema and safety annotations, the essentials are present. However, with no output schema, the description gives no hint of what an insight record contains or how results are paginated, leaving a modest gap.

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% (host, limit, search, api_key, project_id all documented), so the schema carries parameter meaning. The description only implies project scoping ('for a project') and adds no format or syntax detail beyond the schema.

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?

States a specific verb ('List') and resource ('saved PostHog insights (charts)') scoped to a project. It does not name or contrast with the sibling insight-adjacent tools (posthog_query, posthog_list_feature_flags), so sibling differentiation is left to the reader.

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 word 'saved' subtly implies this returns stored insights rather than ad-hoc query results, which is implied guidance. But there is no explicit statement of when to use this over posthog_query or how to scope/filter, so usage is only inferable.

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

Deploy Server

Other Tools