Skip to main content
Glama

get analytics user created

Retrieve daily user creation statistics from TabNews to analyze platform growth trends and user acquisition patterns.

Instructions

To get how many users were created (per day) in tabnews

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the MCP tool 'get analytics user created'. It calls the getAnalyticsUserCreated service function, formats the result as MCP text content with JSON, and handles errors.
    handler: async (): Promise<McpResponse> => {
      try {
        const result = await getAnalyticsUserCreated();
    
        const content: McpTextContent = {
          type: "text",
          text: `Analytics User Created:\n\n${JSON.stringify(result, null, 2)}`,
        };
    
        return {
          content: [content],
        };
      } catch (error) {
        if (error instanceof Error) {
          throw new Error(
            `Failed to get analytics user created: ${error.message}`
          );
        } else {
          throw new Error("Failed to get analytics user created");
        }
      }
    },
  • src/index.ts:59-64 (registration)
    Registers the 'get analytics user created' tool with the MCP server by providing its name, description, parameters schema, and handler function.
    server.tool(
      getAnalyticsUserCreatedTool.name,
      getAnalyticsUserCreatedTool.description,
      getAnalyticsUserCreatedTool.parameters,
      getAnalyticsUserCreatedTool.handler
    );
  • Core service function that fetches the analytics data for users created from the TabNews API endpoint '/analytics/users-created'.
    export async function getAnalyticsUserCreated(): Promise<
      AnalyticsUserCreated[]
    > {
      const response = await fetch(`${TABNEWS_API_URL}/analytics/users-created`);
      const data = await response.json();
    
      return data as AnalyticsUserCreated[];
    }
  • TypeScript interface defining the structure of the analytics data returned by the tool (array of objects with date and number of user registrations).
    export interface AnalyticsUserCreated {
      date: string;
      cadastros: number;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves analytics data, implying a read-only operation, but doesn't specify authentication needs, rate limits, error conditions, or output format. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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

Conciseness4/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, though it could be slightly more structured by explicitly separating purpose from context.

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 the tool's simplicity (0 parameters, no output schema), the description is minimally adequate. It explains what the tool does but lacks details on behavioral traits like authentication or output format. Without annotations or output schema, the description should ideally provide more context about the return data (e.g., date range, aggregation method).

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?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it correctly doesn't mention any. A baseline of 4 is appropriate for a zero-parameter tool with complete schema coverage.

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 clearly states the tool's purpose: 'To get how many users were created (per day) in tabnews'. It specifies the verb ('get'), resource ('users created'), and temporal scope ('per day'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get contents' or 'get status', which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for usage, or comparisons to sibling tools like 'get analytics child content published' or 'get contents by user'. The agent must infer usage solely from the purpose statement.

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/renant/mcp-tabnews'

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