Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

OpenPanel: Get page views

openpanel_get_page_views
Read-only

Retrieves page view statistics for a site through the Insights API, with optional date range and project ID filters, so you can analyze traffic and measure content performance.

Instructions

[UNIFIED] Get page view statistics via Insights API.

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>"
    },
    "name": "openpanel_get_page_views"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
date_rangeNo30d
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered. Beyond that the description adds nothing: it does not say whether results are aggregated totals or a time series, whether the default 30d window is fixed or rolling, or what the response shape looks like for a tool with no output schema.

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?

It is a single short, front-loaded sentence with no filler, which is good structurally. But the brevity is achieved by omitting everything essential, so length is not matched to the tool's complexity.

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

Completeness2/5

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

For a three-parameter analytics query with no output schema, the description should clarify the aggregation level, date-range format, and site identifier semantics. None of that is present, leaving an agent to guess at invocation details.

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

Parameters2/5

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

Schema description coverage is 0% and the description compensates for none of it. The required 'site' parameter has no stated format (slug, URL, or numeric id), and 'date_range' is an unconstrained string with only a default value, so an agent cannot infer accepted syntax from either source.

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?

States a specific verb and resource: retrieving page view statistics via the Insights API. However, the '[UNIFIED]' prefix is unexplained, and the description gives no clue how this differs from siblings like openpanel_get_top_pages or openpanel_get_overview_report, which plausibly return overlapping data.

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 when-to-use guidance, no prerequisites, and no mention of when to prefer this over other reporting tools such as get_top_pages or get_overview_report. The only implied context is 'via Insights API', which is provenance rather than selection guidance.

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