Skip to main content
Glama

mcp-posthog__error-tracking-symbol-sets-list

Read-onlyIdempotent

List source map symbol sets for the current project. Supports pagination plus filtering by exact ref or upload status (valid, invalid, or all) and sorting with order_by. Each result includes has_uploaded_file so you can tell whether the download tool will work. 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-symbol-sets-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoExact symbol set reference to filter by.
limitNoNumber of results to return per page.
offsetNoThe initial index from which to return the results.
searchNoCase-insensitive substring search across reference, release version, release project, and release commit SHA.
statusNoUpload status filter: `valid` has an uploaded file, `invalid` is missing a file, `all` returns both. * `all` - all * `valid` - valid * `invalid` - invalidall
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)
order_byNoSort order for symbol sets. Prefix with `-` for descending order. * `created_at` - created_at * `-created_at` - -created_at * `ref` - ref * `-ref` - -ref * `last_used` - last_used * `-last_used` - -last_used
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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds value with the `has_uploaded_file` field semantics that gates the download flow. The "marked read-only, so it runs straight away" clause largely restates the annotations, but the return-field context is genuine added information.

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?

Front-loaded with the core purpose, then filtering, then the download-gating field. Mostly efficient, though the trailing "Through Royally / read-only" sentence spends words on what annotations already state.

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?

Ten parameters, mostly analytics plumbing, but the functional ones are covered by a fully-described schema, and the description explains pagination and one key return field. With no output schema, it could say more about result shape, but an agent has enough to call it correctly.

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 the schema already documents `ref`, `status` enum values, `order_by` sort keys and pagination. The description merely echoes exact-`ref` and status filtering, adding no format or precedence detail beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List source map symbol sets") plus the scope ("for the current project"), and distinguishes itself from the download sibling by explaining that `has_uploaded_file` tells you whether the download tool will work.

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?

Gives clear invocation context: use it to find symbol sets, filter by exact `ref` or upload `status`, and check `has_uploaded_file` before attempting a download. It stops short of explicit when-not-to-use exclusions, such as preferring the retrieve tool for a single known set.

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