Skip to main content
Glama

Tally by Outpost

Page engagement

get_engagement
Read-onlyIdempotent

How pages are read: views, median reading time, average scroll depth and the share read to the end, per page and overall, and the common entry and exit pages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_engagement"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoA custom range's last day (YYYY-MM-DD), with from.
fromNoA custom range's first day (YYYY-MM-DD), with to. Up to 366 days, not past today.
siteNoThe site's id. Optional: the API key's site is the one read.
limitNoRows at most (default 25).
periodNoA preset period, in the site's time zone. Leave out for the tool's default, or give from and to instead.
filtersNoVisits that match every filter (AND). Each dimension at most once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful behavioral fact that results are both per-page and overall and include entry/exit pages, but says nothing about default period, row limits, ordering, or pagination behavior beyond the schema.

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?

One compact sentence with the headline metrics front-loaded and no filler. The trailing clause ('and the share read to the end, per page and overall, and the common entry and exit pages') stacks several ideas and is slightly tangled, but nothing is wasted.

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

Completeness3/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 usefully names the returned metrics and notes the per-page plus overall split. It still leaves the agent guessing about default period/limit behavior, row ordering, and how the 'overall' figure is surfaced in the response, which matters for a metrics tool with a nested filter object.

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%, including the nested filters object with per-field descriptions and the from/to vs period interplay, so the schema carries the parameter burden. The description adds no parameter meaning (it never mentions period, limit, site, or filters), which meets the baseline for full-coverage schemas but no more.

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 enumerates exactly what comes back: per-page views, median reading time, average scroll depth, share read to the end, plus entry and exit pages, with an 'overall' aggregate. That is specific enough to separate it from generic siblings like get_overview or get_breakdown, though it is framed as a content summary ('How pages are read') rather than a verb+resource statement of what the tool does.

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 any alternative such as get_breakdown or get_overview for per-page or aggregate reporting. The agent must infer from the metric list alone whether this or a sibling tool is the right call.

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