Skip to main content
Glama

get analytics child content published

Retrieve daily comment counts for TabNews content to analyze engagement and track discussion activity over time.

Instructions

To get how many comments were made (per day) in tabnews

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler that invokes the analytics service and formats the response as JSON text content.
    handler: async (): Promise<McpResponse> => {
      try {
        const result = await getAnalyticsChildContentPublished();
    
        const content: McpTextContent = {
          type: "text",
          text: `Analytics Child Content Published:\n\n${JSON.stringify(
            result,
            null,
            2
          )}`,
        };
    
        return {
          content: [content],
        };
      } catch (error) {
        if (error instanceof Error) {
          throw new Error(
            `Failed to get analytics child content published: ${error.message}`
          );
        } else {
          throw new Error("Failed to get analytics child content published");
        }
      }
    },
  • src/index.ts:73-78 (registration)
    Registration of the tool in the MCP server using server.tool().
    server.tool(
      getAnalyticsChildContentPublishedTool.name,
      getAnalyticsChildContentPublishedTool.description,
      getAnalyticsChildContentPublishedTool.parameters,
      getAnalyticsChildContentPublishedTool.handler
    );
  • API service helper that fetches child content published analytics data from TabNews API endpoint.
    export async function getAnalyticsChildContentPublished(): Promise<
      AnalyticsChildContentPublished[]
    > {
      const response = await fetch(
        `${TABNEWS_API_URL}/analytics/child-content-published`
      );
      const data = await response.json();
    
      return data as AnalyticsChildContentPublished[];
    }
  • TypeScript interface defining the structure of the analytics child content published data (output schema).
    export interface AnalyticsChildContentPublished {
      date: string;
      respostas: number;
    }
  • Input parameters schema using Zod (empty object, no parameters required).
    parameters: {},
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 comment counts per day but doesn't cover aspects like authentication needs, rate limits, data freshness, or response 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.

Conciseness5/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's front-loaded with the core functionality and avoids redundancy, making it highly concise and well-structured.

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 complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It explains what the tool does but lacks details on behavior, output format, or usage context. For a simple retrieval tool, it meets basic needs but could be more informative.

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 input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description adds context by specifying the tool returns comment counts aggregated per day, which is useful semantic information beyond the empty schema. This compensates adequately for the lack of parameters.

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 comments were made (per day) in tabnews'. It specifies the verb ('get'), resource ('comments'), and temporal scope ('per day'), though it doesn't explicitly differentiate from sibling tools like 'get comments' or 'get analytics root content published'. The purpose is specific but lacks sibling comparison.

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, exclusions, or comparisons to sibling tools such as 'get comments' or 'get analytics user created'. Usage is implied by the purpose statement alone, with no explicit context for selection.

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