Skip to main content
Glama
mikusnuz

umami-mcp

get_session_data_properties

Retrieve session data property names and data types for a website within a specified time range.

Instructions

Get session data property names and their data types for a website

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
websiteIdYesWebsite UUID
startAtYesStart timestamp in milliseconds
endAtYesEnd timestamp in milliseconds

Implementation Reference

  • The handler, schema, and registration are all in one block via the McpServer.tool() call. The handler makes a GET request to /api/websites/${websiteId}/session-data/properties with startAt and endAt query parameters and returns the JSON result.
    server.tool(
      "get_session_data_properties",
      "Get session data property names and their data types for a website",
      {
        websiteId: z.string().describe("Website UUID"),
        startAt: z.number().describe("Start timestamp in milliseconds"),
        endAt: z.number().describe("End timestamp in milliseconds"),
      },
      async ({ websiteId, startAt, endAt }) => {
        const data = await client.call(
          "GET",
          `/api/websites/${websiteId}/session-data/properties`,
          undefined,
          { startAt, endAt }
        );
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Input schema using Zod: websiteId (string), startAt (number), endAt (number) - all required.
    {
      websiteId: z.string().describe("Website UUID"),
      startAt: z.number().describe("Start timestamp in milliseconds"),
      endAt: z.number().describe("End timestamp in milliseconds"),
    },
  • Registered via server.tool('get_session_data_properties', ...) inside registerSessionTools() in src/tools/sessions.ts. Called from src/index.ts line 31.
    server.tool(
      "get_session_data_properties",
      "Get session data property names and their data types for a website",
      {
        websiteId: z.string().describe("Website UUID"),
        startAt: z.number().describe("Start timestamp in milliseconds"),
        endAt: z.number().describe("End timestamp in milliseconds"),
      },
      async ({ websiteId, startAt, endAt }) => {
        const data = await client.call(
          "GET",
          `/api/websites/${websiteId}/session-data/properties`,
          undefined,
          { startAt, endAt }
        );
        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 are provided, so the description carries full burden. It only states the output (property names and data types) without mentioning side effects, auth requirements, rate limits, or any behavioral traits such as whether it reads or mutates data.

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 sentence with no unnecessary words. It efficiently conveys the tool's purpose without verbosity.

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?

Given no output schema and no annotations, the description is somewhat incomplete. It does not specify the return format (e.g., list of objects) or provide examples. However, the input schema is fully described and the tool's goal is straightforward.

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 description coverage is 100% for all three parameters, so the baseline is 3. The description adds no additional meaning beyond the schema; it does not explain how the date range affects the returned properties or any format requirements.

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 verb 'Get' and the resource 'session data property names and their data types for a website'. It distinguishes from siblings like get_session_data_values (which returns values) and get_session_properties (likely returns properties with values).

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?

The description implies usage for retrieving the schema of session data properties but does not explicitly state when to use this tool over alternatives or provide exclusion criteria. No when-not or alternative tool naming is given.

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