Skip to main content
Glama

mcp-posthog__error-tracking-recommendations-list

Read-onlyIdempotent

List error tracking recommendations for the current project. Each row is a server-computed suggestion with a fixed type and a type-specific meta payload.

Use this when the user asks how to improve their error tracking setup, what they should fix, or wants to act on their recommendations.

Surface only the few recommendations that matter — don't dump every row. Skip ones that are already done or dismissed.

Response envelope (every recommendation)

  • type: one of alerts, rate_limits, source_maps.

  • meta: type-specific payload — see the per-type sections below.

  • completed: true means the recommended action is already satisfied. Nothing to do — skip it.

  • dismissed_at: set if the user dismissed this recommendation. Skip dismissed ones unless the user explicitly asks.

Only act on recommendations that are not completed and not dismissed.

Recommendation types

  • alerts — meta.alerts is a list of { key, enabled } for the issue-created/issue-reopened/issue-spiking triggers; … 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": {
      "context": "<context>"
    },
    "name": "mcp-posthog__error-tracking-recommendations-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pollNoTrue reads the current state without scheduling a refresh.
limitNoNumber of results to return per page.
offsetNoThe initial index from which to return the results.
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
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real value: the response envelope, the `completed` and `dismissed_at` semantics, and the enumeration of `type` values. The trailing text is garbled/truncated ('… Through Royally: its server marks it read-only'), which weakens an otherwise strong disclosure.

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 front-loaded purpose and the header-delimited response envelope are well organized, but the definition ends in a corrupted fragment that reads as noise rather than content. The per-type section is also cut off mid-sentence, so structure is undermined by truncation.

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?

With no output schema, the description correctly takes on the burden of explaining return values via the response envelope and per-type `meta` payloads. The truncation leaves the `alerts`/`rate_limits`/`source_maps` detail incomplete, which is the main 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%, so `poll`, `limit`, `offset`, `context`, `site_id`, `llm_model`, and `conversation_id` are all documented in the schema. The description adds nothing about pagination or the `poll` flag, so the 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 first sentence gives a specific verb and resource ('List error tracking recommendations for the current project') and explains the row shape (server-computed suggestion with fixed `type` and type-specific `meta`). It is clearly distinct from the sibling rules-list tools, though it never names them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a concrete trigger ('when the user asks how to improve their error tracking setup, what they should fix, or wants to act on their recommendations') and gives when-not guidance ('Skip ones that are already done or dismissed', 'don't dump every row'). No alternative tool is named, so it falls short of a 5.

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