Skip to main content
Glama
Sign In
@vskstudio/takt-mcp

@vskstudio/takt-mcp

Official
by taktlytics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_breakdown

Retrieve top values of website analytics dimensions like pages, sources, or countries for a specific domain and period.

Instructions

Top values of a dimension for a site (e.g. top pages, traffic sources, countries, devices, browsers).

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": {
      "domain": "<domain>",
      "dimension": "<dimension>"
    },
    "name": "get_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD (use with `from`).
tzNoIANA timezone for bucketing, e.g. Europe/Paris.
fromNoStart date YYYY-MM-DD (use with `to` for a custom range).
limitNoMax rows (default 10).
domainYesSite domain.
periodNoPreset period (default 7d). Ignored when both `from` and `to` are set.
countryNoRestrict to one country (ISO-3166 alpha-2, e.g. FR).
dimensionYesDimension to rank.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, and description omits behavioral traits such as default ordering, limit behavior, time zone handling, or what 'top' means. It only states the basic purpose without operational details.

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?

Single sentence, zero waste, and front-loaded with purpose. However, it could be improved by adding a brief usage context without sacrificing conciseness.

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?

Given no output schema and no annotations, the description should compensate more. It provides only the core purpose, missing return format, pagination, and error handling. Adequate for simple expected behavior but not complete.

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 coverage is 100%, so each parameter already has a description. The tool description adds no additional meaning beyond the schema, thus baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it returns top values of a dimension (verb 'top values' + resource 'dimension for a site'), with concrete examples (pages, sources, etc.) that differentiate it from siblings like get_funnels or get_timeseries.

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?

No explicit guidance on when to use this tool vs alternatives. The examples imply context but lack when-not or alternative pointers. For a tool with many siblings, this is a gap.

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