Skip to main content
Glama

GetVisitStatisticsTool

Read-only

mcptask.online site traffic, the same numbers as the visit statistics page: one section per call (overview, pages, daily, weekdays, funnel, registrations, referrers, blog_articles), start with the overview. The optional page argument narrows the daily section to one page. Only for owners of the WorkVector company.

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": {
      "account_code": "<account_code>"
    },
    "name": "GetVisitStatisticsTool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOnly for section daily: narrow the series to one page, one of hp, features, about, pricing, autonomous_agents, contact, integrations, integrations_developers, media, installation, onboarding, how_it_works, api_docs, terms, privacy, cookies_policy, press_kit, runner, runner_docs, live, security, ai_coding_agent_orchestrators, vibe_kanban_alternative, devin_alternative, jira_alternative, build_your_own_ai_developer, ai_developer_comparison, linear_alternative, copilot_alternative, openhands_alternative, blog, blog_article
rangeNoPeriod: one of week, four_weeks, four_months, this_month, last_month; defaults to week
sectionNoPart of the statistics: one of overview, pages, daily, weekdays, funnel, registrations, referrers, blog_articles; defaults to overview
account_codeYesAccount code; only "jchsoft" has visit statistics

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / page / description
      Previous value: -"Only for section daily: narrow the series to one page, one of hp, features, about, pricing, autonomous_agents, contact, integrations, integrations_developers, media, installation, onboarding, how_it_works, api_docs, terms, privacy, cookies_policy, press_kit, runner, runner_docs, live, security, ai_coding_agent_orchestrators, vibe_kanban_alternative, devin_alternative, jira_alternative, build_your_own_ai_developer, ai_developer_comparison, linear_alternative, copilot_alternative, blog, blog_article"New value: +"Only for section daily: narrow the series to one page, one of hp, features, about, pricing, autonomous_agents, contact, integrations, integrations_developers, media, installation, onboarding, how_it_works, api_docs, terms, privacy, cookies_policy, press_kit, runner, runner_docs, live, security, ai_coding_agent_orchestrators, vibe_kanban_alternative, devin_alternative, jira_alternative, build_your_own_ai_developer, ai_developer_comparison, linear_alternative, copilot_alternative, openhands_alternative, blog, blog_article"
  2. Changed1 schema field changed
    • changedInput schema / properties / page / description
      Previous value: -"Only for section daily: narrow the series to one page, one of hp, features, about, pricing, autonomous_agents, contact, integrations, integrations_developers, media, installation, onboarding, how_it_works, api_docs, terms, privacy, cookies_policy, press_kit, runner, runner_docs, live, security, ai_coding_agent_orchestrators, vibe_kanban_alternative, devin_alternative, jira_alternative, build_your_own_ai_developer, ai_developer_comparison, linear_alternative, blog, blog_article"New value: +"Only for section daily: narrow the series to one page, one of hp, features, about, pricing, autonomous_agents, contact, integrations, integrations_developers, media, installation, onboarding, how_it_works, api_docs, terms, privacy, cookies_policy, press_kit, runner, runner_docs, live, security, ai_coding_agent_orchestrators, vibe_kanban_alternative, devin_alternative, jira_alternative, build_your_own_ai_developer, ai_developer_comparison, linear_alternative, copilot_alternative, blog, blog_article"
  3. Changed1 schema field changed
    • changedInput schema / properties / page / description
      Previous value: -"Only for section daily: narrow the series to one page, one of hp, features, about, pricing, autonomous_agents, contact, integrations, integrations_developers, media, installation, onboarding, how_it_works, terms, privacy, cookies_policy, press_kit, runner, runner_docs, live, security, ai_coding_agent_orchestrators, vibe_kanban_alternative, devin_alternative, jira_alternative, build_your_own_ai_developer, ai_developer_comparison, linear_alternative, blog, blog_article"New value: +"Only for section daily: narrow the series to one page, one of hp, features, about, pricing, autonomous_agents, contact, integrations, integrations_developers, media, installation, onboarding, how_it_works, api_docs, terms, privacy, cookies_policy, press_kit, runner, runner_docs, live, security, ai_coding_agent_orchestrators, vibe_kanban_alternative, devin_alternative, jira_alternative, build_your_own_ai_developer, ai_developer_comparison, linear_alternative, blog, blog_article"
  4. Changed1 schema field changed
    • changedInput schema / properties / page / description
      Previous value: -"Only for section daily: narrow the series to one page, one of hp, features, about, pricing, autonomous_agents, contact, integrations, integrations_developers, media, installation, onboarding, how_it_works, terms, privacy, cookies_policy, press_kit, runner, runner_docs, live, security, ai_coding_agent_orchestrators, vibe_kanban_alternative, devin_alternative, jira_alternative, build_your_own_ai_developer, ai_developer_comparison, blog, blog_article"New value: +"Only for section daily: narrow the series to one page, one of hp, features, about, pricing, autonomous_agents, contact, integrations, integrations_developers, media, installation, onboarding, how_it_works, terms, privacy, cookies_policy, press_kit, runner, runner_docs, live, security, ai_coding_agent_orchestrators, vibe_kanban_alternative, devin_alternative, jira_alternative, build_your_own_ai_developer, ai_developer_comparison, linear_alternative, blog, blog_article"
  5. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real context beyond them: authorization is limited to WorkVector company owners, results are mirrored from the internal stats page, and 'one section per call' tells the agent it will need multiple invocations to get everything. It does not discuss caching, freshness, or cost limits, keeping it short of a 5.

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?

Two sentences, front-loaded with what the tool returns, then the per-call section rule and the page caveat. The phrase 'the same numbers as the visit statistics page' is somewhat redundant framing but does useful anchoring work.

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 agent gets section names but no sense of the shape of each section's payload (metrics, dimensions, units), and 'one section per call' implies cost without saying how large a response is. For a read-only reporting tool with fully documented parameters this is adequate, but the return side is under-described.

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 all four parameters are already documented, including the page allow-list and range values. The description only restates that page applies solely to the daily section and that overview is the entry point, adding little beyond the schema text.

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 names the concrete resource (mcptask.online site traffic) and anchors it to a known artifact ('the same numbers as the visit statistics page'), then enumerates the eight sections returned. No sibling tool touches traffic analytics, so the tool is easily separable, though the description doesn't explicitly say 'returns/reports' as a verb.

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?

It gives a concrete usage sequence ('start with the overview'), an access precondition ('Only for owners of the WorkVector company'), and a scoping rule for the page argument. There are no true alternatives among siblings, so the absence of explicit comparison is a minor gap rather than a real one.

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