Skip to main content
Glama

mcp-posthog__error-tracking-grouping-rules-list

Read-onlyIdempotent

List error tracking grouping rules for the current project. Returns rules in evaluation order with their filters, optional assignee, description, and linked issue when available. 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-grouping-rules-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the closing sentence about it being read-only and running 'straight away' merely restates structured data and earns no credit. What does add value is the disclosure of return shape — evaluation order, filters, optional assignee, description, linked issue — which no output schema provides.

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 first two sentences are dense and front-load the useful information, but the third sentence is filler that repeats the readOnlyHint annotation and is awkwardly worded ('Through Royally'). It could be dropped without loss, so efficiency is undermined by one redundant clause.

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?

With no output schema, the description usefully covers the returned fields and their ordering, which is the main thing an agent needs. However, it is silent on pagination/limits and on how project scoping is applied, leaving moderate gaps for a list tool whose only parameters are server-side analytics metadata.

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 all four parameters are analytics/context metadata (context, site_id, llm_model, conversation_id) rather than domain filters, so the schema already fully documents them. The description adds no parameter meaning beyond that, which matches the baseline 3 for high-coverage schemas.

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 specific verb and resource ('List error tracking grouping rules') plus scope ('for the current project'), which distinguishes it from the assignment, bypass, severity, and suppression rule-list siblings by resource name. It stops short of explicitly naming those siblings as alternatives, so it is clear but not fully differentiated.

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?

Usage is only implied by the resource name; there is no statement of when to call this versus the sibling rule lists (e.g., grouping vs assignment rules) and no exclusions or prerequisites. An agent can infer the purpose but must guess why it would choose this over a neighboring list tool.

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