Skip to main content
Glama

mcp-posthog__error-tracking-settings-get

Read-onlyIdempotent

Get the error tracking ingestion settings for the current project. Returns ingestion_enabled, which is false when ingestion drops every exception the project sends, and the project-wide and per-issue exception rate limits, where each *_rate_limit_value is the maximum events ingested per bucket and each *_rate_limit_bucket_size_minutes is the bucket window. A null *_rate_limit_value means no limit is set. Also returns ai_issue_summaries_enabled, which is true when the project has turned on AI issue summaries. Read these before updating so you can preserve the fields you don't intend to change. 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-settings-get"
  }
}

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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the closing line ('its server marks it read-only, so it runs straight away') mostly restates that. The genuinely useful behavioral content is the field semantics: what `ingestion_enabled=false` implies, that a null `*_rate_limit_value` means no limit, and how bucket sizes are expressed. That is valuable, but it is return-value semantics rather than added behavioral traits such as scoping or failure modes.

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?

It is front-loaded with the operation and then the field semantics, and each sentence about return fields carries information. The trailing 'Through Royally... runs straight away' sentence is largely redundant with the read-only annotation and slightly promotional, keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 fully compensates by explaining every returned field and the null convention, and it flags the read-before-update workflow. For a simple read-only settings getter, nothing an agent needs in order to call or interpret it is 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 four parameters (context, site_id, llm_model, conversation_id) are already documented, and they are analytics metadata rather than functional inputs. The description adds no input-parameter meaning; its detail is entirely about outputs, which is why 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 description opens with a specific verb and resource: 'Get the error tracking ingestion settings for the current project,' then enumerates the concrete fields returned (ingestion_enabled, rate limits, ai_issue_summaries_enabled). It clearly separates this from the sibling *-list/*-retrieve rule tools by describing a settings read, though it never names the update counterpart it refers to.

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?

'Read these before updating so you can preserve the fields you don't intend to change' gives explicit read-before-write guidance that an agent can act on. It stops short of naming the alternative tool or stating when not to call it, so it is clear context rather than full routing guidance.

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