Skip to main content
Glama
Sign In
posthog-mcp-server

posthog-mcp-server

by friendlygeorge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_person

Retrieve a PostHog user by distinct_id to access their properties, creation date, and event count.

Instructions

Get a PostHog person (user) by their distinct_id. Returns person properties, creation date, and event count.

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": {
      "distinct_id": "<distinct_id>"
    },
    "name": "get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
distinct_idYesThe person's distinct_id to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden for behavioral disclosure. It reveals that the tool returns person properties, creation date, and event count, but does not mention error behavior (e.g., not found) or any side effects. This is acceptable but limited.

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

Conciseness5/5

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

The description is a single, front-loaded sentence that states the action, target, and return value with no unnecessary words. It is highly concise and well-structured.

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 simple single-parameter get tool with no output schema, the description adequately covers purpose and return values. It lacks explicit error-handling details and alternative guidance, but these are minor for this complexity.

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 provides 100% coverage for the distinct_id parameter, describing it as 'The person's distinct_id to look up'. The description adds no additional semantic meaning beyond repeating the identifier, so the baseline of 3 applies.

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

Purpose5/5

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

The description clearly states the tool retrieves a specific PostHog person by distinct_id, using the verb 'Get' with a specific resource and identifier. It distinguishes from sibling tools like list_persons by indicating it fetches a single person by ID.

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 description implies usage when you have a distinct_id, but does not explicitly state when to use this tool versus alternatives such as list_persons. No exclusions or alternative recommendations are provided.

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