Skip to main content
Glama

mcp-posthog__error-tracking-suppression-rules-list

Read-onlyIdempotent

List error tracking suppression rules for the current project. Returns rules in evaluation order with their filters, sampling rate, and disabled state. Supports pagination with limit and offset. 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-suppression-rules-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds real value by disclosing the return shape (rules in evaluation order, with filters, sampling rate, disabled state) and pagination support. The sentence about the server marking it read-only largely restates readOnlyHint and adds little, and no default or maximum page size is given.

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?

The definition is front-loaded with purpose, then return contents, then pagination — a sensible order with no filler sentences. The closing remark about Royally marking it read-only is redundant with the annotations and is the one line that does not earn its place.

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 does the necessary work of describing what comes back and in what order, plus pagination. For a read-only listing tool of this complexity that is nearly complete; only pagination defaults/limits and a hint about total counts are missing.

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 all six parameters, including the context/site_id/llm_model/conversation_id analytics fields, are already documented. The description only restates that limit and offset drive pagination, adding no format, default, or boundary detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

"List error tracking suppression rules for the current project" gives a specific verb (list) and a specific resource (suppression rules), which naturally separates it from the sibling assignment/bypass/grouping/severity rule lists. It stops short of explicitly naming a sibling or stating the contrast, so it is clear but not fully differentiating.

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: an agent can infer this is the tool for inspecting suppression rules scoped to the current project, and the pagination note hints at browsing large sets. There is no statement of when to prefer this over other rule-listing tools, no prerequisites, and no exclusions.

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