Skip to main content
Glama
Sign In
HitKeep

HitKeep

by HitKeep
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

List HitKeep Sites

hitkeep_list_sites
Read-onlyIdempotent

List all HitKeep sites accessible via your API client to determine available analytics properties.

Instructions

List HitKeep sites visible to the bearer API client.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sitesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.1

TDQS

A4.5/5.0
Behavior4/5

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

The readOnlyHint and idempotentHint annotations already cover safety, and the description adds the scoping detail about 'bearer API client' visibility, which is transparent and non-contradictory.

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?

The description is a single, concise, and well-structured sentence that conveys all necessary information without verbosity.

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?

Given the simplicity of the tool (no parameters, straightforward output), the description is complete enough for an agent to understand its purpose and likely return behavior, though it does not detail the output format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so this dimension is trivially satisfied and the description adds no ambiguity.

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 the action ('List') and resource ('HitKeep sites'), and the phrase 'visible to the bearer API client' differentiates it from sibling tools that focus on specific metrics or data.

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 implicitly indicates when to use this tool (to enumerate accessible sites) and does not conflict with sibling tools, though it does not explicitly mention alternatives or exclusion criteria. The context is clear enough.

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