Skip to main content
Glama
Sign In

Anry

by io.anry.mcp
OverviewDiscussionsAdmin

Get top pages

get_top_pages
Read-onlyIdempotent

Per-page metrics for a site over a date window (max 12 months): visitors, sessions, revenue, page views, bounce/exit/conversion rates, ordered by revenue. Use for 'which pages matter' and page-level triage.

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_id": "<site_id>"
    },
    "name": "get_top_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (default 10)
site_idYesSite id from list_sites (UUID)
end_dateNoISO date (YYYY-MM-DD). Defaults to today.
start_dateNoISO date (YYYY-MM-DD). Defaults to 30 days before end_date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: a hard 12-month date-window cap and revenue-descending ordering, both of which affect how results should be interpreted and what happens when a request exceeds the window.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence front-loads the resource and scope, then the metric list and ordering, then the usage cue. No filler, no restatement of the title, and every clause carries information the agent needs.

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 correctly compensates by enumerating the returned fields and their sort order, which is the main thing an agent needs to interpret results. Minor gaps remain around result truncation semantics and what an empty result means, but the definition is otherwise sufficient for a read-only analytics tool.

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

Parameters4/5

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

Schema description coverage is 100%, which sets a baseline of 3, and the description goes beyond it by imposing a maximum 12-month span on start_date/end_date that the schema does not state. It also implicitly prioritizes the limit parameter by declaring revenue ordering, meaning limit truncates the highest-revenue pages.

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?

Names a specific resource (pages) and enumerates the exact metrics returned (visitors, sessions, revenue, page views, bounce/exit/conversion rates) plus the ordering (by revenue), so the agent knows precisely what comes back. It does not name a sibling, but 'per-page' and 'page-level triage' implicitly separate it from get_analytics_overview and get_traffic_sources.

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?

'Use for which pages matter and page-level triage' gives a clear situational trigger for selection. It stops short of naming the alternative tool to pick for site-wide or channel-level questions, so routing between this and get_analytics_overview / get_traffic_sources still requires inference.

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

All Anry toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources