Skip to main content
Glama

posthog_list_feature_flags

Read-onlyIdempotent

List feature flags for a PostHog project by providing an API key and optional host or project ID.

Instructions

List PostHog feature flags 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_feature_flags"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoPostHog host (default https://us.posthog.com)
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. The description only confirms the list is per-project, which adds a small amount of behavioral context but nothing on pagination or result volume.

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 waste. It is efficient but very thin, leaving no room for the scoping caveats an agent might want.

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?

Rich annotations and a fully documented schema cover most of what's needed, and there is no output schema to explain. However, for a listing endpoint the description says nothing about result size, pagination, or whether the project default is resolved from configuration — a gap worth one sentence.

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 api_key, host and project_id are already documented in the schema. The description adds no parameter-level detail beyond the word 'project', so baseline 3 applies.

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?

Names a specific verb and resource ('List PostHog feature flags') and scopes it to a project, which separates it from siblings like posthog_query and posthog_list_insights. It is clear but doesn't explicitly contrast with those siblings.

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 on when to use this versus posthog_query (arbitrary queries) or the other posthog_list_* tools. The agent must infer from the name that this is the enumeration path for feature flags.

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