Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

OpenPanel: Track screen view

openpanel_track_screen_view
Destructive

Track screen view events for mobile applications by specifying the site and screen name, with optional metadata for profile, properties, client IP, and user agent.

Instructions

[UNIFIED] Track a screen view event for mobile applications.

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": {
      "site": "<site>",
      "screen_name": "<screen_name>"
    },
    "name": "openpanel_track_screen_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
client_ipNo
profile_idNo
propertiesNo
user_agentNo
screen_nameYes
screen_classNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=true, so the write/destructive profile is covered. The description adds nothing beyond that: it does not explain event ingestion behavior, whether duplicate screen views are deduplicated, what profile_id/client_ip resolution does, or what happens on failure.

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 a single tightly worded sentence with the key noun phrase front-loaded. The only waste is the meaningless "[UNIFIED]" tag, and brevity here comes at the cost of under-specification rather than verbosity.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 7-parameter event-ingestion tool with no output schema and no annotation-explained return behavior deserves substantially more: which parameters are meaningful for mobile screen views, how profile_id vs client_ip interact, and the expected response are all absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 7 parameters at 0% description coverage, including required fields (site, screen_name) and ambiguous optional ones (profile_id, properties, client_ip, user_agent, screen_class). The description mentions none of them, so an agent gets no meaning beyond raw names and types.

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 pairs a specific verb ("Track") with a specific resource ("screen view event") and adds a scope qualifier ("mobile applications"), which implicitly separates it from openpanel_track_page_view. The "[UNIFIED]" prefix is opaque noise, and no sibling is named explicitly, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this versus openpanel_track_event, openpanel_track_batch, or openpanel_track_page_view. The only routing signal is the incidental phrase "for mobile applications," which the agent must infer means this is the mobile counterpart to page views.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools