Skip to main content
Glama

Tagely Analytics

Traffic and conversion totals

get_summary
Read-onlyIdempotent

Headline numbers for a date range: page views (all, and excluding bots), unique visitors, new visitors, conversions, conversion rate and event counts by type. These match the Tagely analytics page. Set compare_to_previous to also get the preceding period.

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoDate range. last_7_days / last_30_days end yesterday (today excluded), as on the Tagely analytics page. Default last_7_days, or custom if start_date is given.
end_dateNoYYYY-MM-DD, for period=custom (inclusive). A custom range covers at most 366 days.
start_dateNoYYYY-MM-DD, for period=custom (inclusive).
compare_to_previousNoAlso return the same figures for the preceding period: the previous calendar month for last_month, the same days of last month so far for this_month, otherwise the period of equal length immediately before.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely useful behavioral fact - the numbers are consistent with the Tagely analytics page - but says nothing about response shape, latency, or data freshness beyond that.

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?

Two sentences, both front-loaded with the most decision-relevant information: first what the tool returns, then the optional comparison behavior. No filler, no repetition of the tool name, and the metric list is dense rather than padded.

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?

There is no output schema, and the description compensates well by enumerating the returned metrics, which is the main thing an agent needs to know to decide whether to call it. It does not explain the shape of the returned object or how bot-excluded views relate to the total, leaving a small gap for a no-output-schema tool.

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 enum values, the YYYY-MM-DD format, the 366-day custom cap and the compare_to_previous comparison semantics are all already documented in the schema. The description's 'Set compare_to_previous to also get the preceding period' merely restates that field rather than adding new meaning, so the baseline of 3 applies.

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 gives a specific resource (headline totals for a date range) and enumerates exactly which metrics come back: page views including/excluding bots, unique and new visitors, conversions, conversion rate and event counts by type. That is far more concrete than a bare restatement of the name. It stops short of naming the natural alternative (get_breakdown) for deeper segmentation, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

Usage is only implied: 'Headline numbers for a date range' plus a note that setting compare_to_previous adds the preceding period. There is no explicit statement of when to pick this over get_breakdown or get_visitor_journey, and no guidance on prerequisites or limits beyond what the schema already carries.

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