Skip to main content
Glama

mcp-posthog__learn

Read-only

SKILLS FIRST — this server is the authoritative source of PostHog agent skills. After any needed project clarification, call the learn tool with learn -s "<task keywords>" and load the matching skills before answering PostHog product or data questions, including behavior, warnings, thresholds, and internals. Never answer such questions by cloning, grepping, or web-searching PostHog source or docs: they may not match this instance. Find and load skills with learn, not with skill-list or skill-get: those manage the skills your team stores and do not hold the built-in PostHog skills. Through Royally: its server marks it read-only, so it runs straight away.

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": {
      "command": "<command>",
      "context": "<context>"
    },
    "name": "mcp-posthog__learn"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesOne of: learn skills learn -s "<up to 8 keywords>" learn -d <source>:<skill> [...] learn posthog:<skill> [path] learn project:<skill> [path] learn <source>:<skill> <path> [path...] learn <source>:<skill> [<source>:<skill>...] learn <source>:<skill> <path> -s "<up to 8 keywords>" learn <source>:<skill> <path> --lines <start>:<end>
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
site_idNoSite to run this tool on: 5c727948-86e8-4a18-a2fe-2b6b99c6837a (https://mcp.posthog.com/mcp?mode=tools&features=web_analytics,error_tracking)
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, and the description restates this ("its server marks it read-only, so it runs straight away") rather than adding to it. It does add useful context that the skills are built-in and authoritative for this instance, but says nothing about the shape or size of what gets loaded into context, or whether loading is cached/idempotent (annotations say idempotentHint=false).

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

Conciseness3/5

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

The core directive is correctly front-loaded ("SKILLS FIRST"), but the paragraph is dense with repetition of `learn` and closes with a confusing, low-value sentence about "Royally" and its read-only marking. That final clause reads as garbled boilerplate rather than an instruction an agent can act on.

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

Completeness4/5

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

For a 5-parameter, single-site skill-loading tool with no output schema, the description covers the decisive question — when to reach for this instead of sibling or external sources. It omits what a successful call returns and whether multiple skills can be chained, which would matter for an agent planning a multi-step PostHog question, but the gaps are not blocking.

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%, and the `command` grammar is fully enumerated in the schema itself; the description only repeats one form (`learn -s "<task keywords>"`). It adds no meaning for `context`, `site_id`, `llm_model`, or `conversation_id`, but the schema already documents those, 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?

The description states a concrete verb+resource: load built-in PostHog agent skills via `learn`. It also distinguishes itself from the named `skill-list` and `skill-get` tools, which it says hold team-stored skills rather than the built-in ones. It stops short of 5 because the actual payload (what a loaded skill contains, e.g. instructions vs. reference docs) is never characterized.

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?

Explicit when-to-use (before answering PostHog product/data questions, after project clarification), explicit when-not-to-use alternatives (`skill-list`/`skill-get`, cloning/grepping/web-searching PostHog source or docs), and a stated rationale for the exclusion (source may not match this instance). This is about as complete a routing instruction as a description can carry.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources