Skip to main content
Glama

Posthog Get Events

posthog_get_events
Read-onlyIdempotent

Fetch recent events from a PostHog project. Returns event names, timestamps, and properties. Example: get_events({ project_id: "12345", limit: 50, apiKey: "phx..." })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 50,
      "_apiKey": "your-posthog-api-key",
      "project_id": "12345"
    },
    "name": "posthog_get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax events to return (default 100, max 1000)
_apiKeyYesPostHog personal API key (phx_...)
project_idYesPostHog project ID (numeric string)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds that results include event names, timestamps and properties, which is genuine but minimal context beyond the structured fields. It says nothing about pagination, rate limits, or what 'recent' means in practice.

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?

Three short sentences with the purpose front-loaded, followed by return content and a concrete call example. Nothing is padded, though the example duplicates the schema's own examples array.

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?

An output schema exists, so the description need not explain return structure, and annotations cover behavior. However, for a data-retrieval tool it omits any guidance on result volume, pagination, or recency window, leaving gaps an agent must discover empirically.

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 limit (default 100, max 1000), _apiKey format and project_id type are already fully documented. The example invocation shows the parameters in use but adds no meaning the schema does not already carry; 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?

States a specific verb and resource: 'Fetch recent events from a PostHog project', and even names the fields returned. It is distinguishable from get_persons and get_insights by the 'events' resource, though the description never explicitly contrasts itself 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?

There is no statement of when to use this tool versus alternatives such as get_persons or get_insights, and no prerequisites or exclusions. 'Recent events' hints at a recency scope but leaves the agent to infer selection criteria.

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.