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

@vskstudio/takt-mcp

Official
by taktlytics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_sites

Retrieve all sites (domains) in your organization to manage analytics data, requiring sites:read permission.

Instructions

List the sites (domains) in an organization. Requires a key with the sites:read permission.

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": "list_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoOrg slug. Defaults to TAKT_ORG if set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It only mentions a permission requirement. It does not describe other behaviors such as pagination, sorting, rate limits, or what happens when no sites exist.

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?

The description is concise with two sentences, each providing useful information. It is front-loaded with the purpose. However, it could be expanded slightly without becoming verbose.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple but lacks output format description, error handling, or any additional context beyond listing sites. No output schema exists, so the description should compensate but does not.

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% with a description for the 'org' parameter. The description adds no meaning beyond the schema, so a 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?

The description clearly states 'List the sites (domains) in an organization' using a specific verb and resource. It distinguishes itself from sibling tools that focus on analytics reports (get_breakdown, get_funnels, etc.).

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?

The description includes a prerequisite ('Requires a key with the sites:read permission') and the context is clear given the sibling tools have different purposes. However, it does not explicitly state when not to use this tool or mention alternatives.

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