Skip to main content
Glama
mikusnuz

umami-mcp

get_website

Retrieve detailed information about a specific website using its unique UUID identifier.

Instructions

Get details of a specific website by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
websiteIdYesWebsite UUID

Implementation Reference

  • Handler function for 'get_website' tool. Takes a websiteId string, calls the Umami API to GET /api/websites/{websiteId}, and returns the website details as JSON text content.
    async ({ websiteId }) => {
      const data = await client.call("GET", `/api/websites/${websiteId}`);
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Input schema for 'get_website' tool — requires a single 'websiteId' string parameter (the website's UUID).
    {
      websiteId: z.string().describe("Website UUID"),
    },
  • Registration of 'get_website' tool via server.tool(...) inside registerWebsiteTools(). The tool is named 'get_website' with description 'Get details of a specific website by ID'.
    server.tool(
      "get_website",
      "Get details of a specific website by ID",
      {
        websiteId: z.string().describe("Website UUID"),
      },
      async ({ websiteId }) => {
        const data = await client.call("GET", `/api/websites/${websiteId}`);
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
Behavior2/5

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

No annotations provided, and description only says 'Get details' without mentioning read-only nature, error handling, or any side effects.

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 succinct sentence with no unnecessary words or redundancy.

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?

Sufficient for a simple retrieval tool, but lacks explanation of what 'details' includes; no output schema defined.

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?

100% schema coverage already describes parameter 'websiteId'; description adds no extra meaning beyond 'by ID'.

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 verb 'Get' and resource 'details of a specific website', distinguishing it from 'list_websites' which returns all websites.

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 versus alternatives like 'create_website' or 'list_websites'; usage is implied by name and parameter.

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/mikusnuz/umami-mcp'

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