Skip to main content
Glama
Defilan

Plausible Analytics MCP Server

by Defilan

list-sites

Retrieve a list of all websites you have access to in Plausible Analytics for quick navigation and management.

Instructions

List all sites you have access to in Plausible Analytics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'list-sites' tool registration and handler. Calls client.listSites() and returns the result as JSON text.
    server.tool(
      "list-sites",
      "List all sites you have access to in Plausible Analytics",
      {},
      async () => {
        const sites = await client.listSites();
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(sites, null, 2),
            },
          ],
        };
      }
    );
  • The listSites() method on PlausibleClient that calls the Plausible API v1 /api/v1/sites endpoint with pagination, collecting and returning all sites.
    async listSites(): Promise<PlausibleSite[]> {
      const sites: PlausibleSite[] = [];
      let hasMore = true;
      let page = 1;
    
      while (hasMore) {
        const response = await fetch(
          `${this.baseUrl}/api/v1/sites?page=${page}&limit=100`,
          {
            headers: {
              Authorization: `Bearer ${this.apiKey}`,
            },
          }
        );
    
        if (!response.ok) {
          const body = await response.text();
          throw new Error(
            `Plausible API error (${response.status}): ${body}`
          );
        }
    
        const data = (await response.json()) as { sites: PlausibleSite[] };
        sites.push(...data.sites);
        hasMore = data.sites.length === 100;
        page++;
      }
    
      return sites;
    }
  • The PlausibleSite interface used as the return type for listSites(), containing domain and timezone.
    export interface PlausibleSite {
      domain: string;
      timezone: string;
    }
  • src/index.ts:25-40 (registration)
    Registration of the 'list-sites' tool using server.tool() on the McpServer instance. No input schema (empty object {}) since no parameters are needed.
    server.tool(
      "list-sites",
      "List all sites you have access to in Plausible Analytics",
      {},
      async () => {
        const sites = await client.listSites();
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(sites, null, 2),
            },
          ],
        };
      }
    );
Behavior2/5

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

No annotations provided. Description does not disclose read-only nature, potential limits, or output format. Minimal information beyond core purpose.

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?

Single sentence, no fluff, front-loaded with action and resource.

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?

Adequate for a simple parameterless tool, but lacks details on response structure or pagination. Marginal given absence of output schema or annotations.

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

Parameters4/5

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

No parameters exist, so description cannot add parameter meaning. Baseline score of 4 applies as there is nothing to add.

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?

Clearly states the action (list) and resource (sites) with scope (all you have access to). Distinct from sibling tools that deal with analytics data.

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?

Implies usage when needing to see accessible sites. No explicit when-to-use or alternatives, but siblings are obviously different.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Defilan/plausible-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server