Skip to main content
Glama
lindoai

mcp-lindoai

Official

get_website_analytics

Read-only

Fetch website analytics data by providing the website ID. Access performance metrics and visitor insights to evaluate site performance.

Instructions

Get website analytics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID

Implementation Reference

  • The async handler function that executes the tool logic: calls the API endpoint /v1/workspace/website/{website_id}/analytics via GET and returns the data as JSON text content.
    async ({ website_id }) => {
      const data = await apiCall(`/v1/workspace/website/${website_id}/analytics`, "GET");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Input schema for the tool: requires a 'website_id' string parameter.
    {
      website_id: z.string().describe("The website ID"),
    },
  • Registration of the tool via server.tool() with name 'get_website_analytics' and description 'Get website analytics.'
    server.tool(
      "get_website_analytics",
      "Get website analytics.",
      {
        website_id: z.string().describe("The website ID"),
      },
      { title: "Get Website Analytics", readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      async ({ website_id }) => {
        const data = await apiCall(`/v1/workspace/website/${website_id}/analytics`, "GET");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • The apiCall helper function used by the handler to make authenticated HTTP requests to the Lindo AI API.
    async function apiCall(path, method, body) {
      const url = `${BASE_URL}${path}`;
      const res = await fetch(url, {
        method,
        headers: {
          Authorization: `Bearer ${API_KEY}`,
          "Content-Type": "application/json",
        },
        ...(body ? { body: JSON.stringify(body) } : {}),
      });
      return res.json();
    }
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds no behavioral context beyond that, such as what 'analytics' includes, data format, or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short (3 words), which is concise but at the expense of completeness. Front-loaded but overly minimal.

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?

No output schema and no description of return values. The tool name implies analytics, but details like metrics, date ranges, or aggregation are missing, leaving the agent uncertain about what to expect.

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 has 100% coverage for the single parameter 'website_id', described as 'The website ID'. Description does not add extra meaning beyond the schema.

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

Purpose4/5

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

The description 'Get website analytics' clearly indicates the action (get) and resource (website analytics). It distinguishes from siblings like 'get_website' (to get website info) and 'get_workspace_analytics' (workspace-level), but lacks explicit differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives (e.g., 'get_workspace_analytics'). No mention of prerequisites, limitations, or when not to use.

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/lindoai/mcp-server'

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