Skip to main content
Glama

get analytics root content published

Retrieve daily post publication counts from TabNews to analyze content trends and publishing patterns.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool definition including the handler function that executes the tool logic: fetches analytics data from service, formats as JSON text in McpResponse, and handles errors.
    export const getAnalyticsRootContentPublishedTool = {
      name: "get analytics root content published",
      description: "To get how many posts were made (per day) in tabnews",
      parameters: {},
      handler: async (): Promise<McpResponse> => {
        try {
          const result = await getAnalyticsRootContentPublished();
    
          const content: McpTextContent = {
            type: "text",
            text: `Analytics Root 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 root content published: ${error.message}`
            );
          } else {
            throw new Error("Failed to get analytics root content published");
          }
        }
      },
    };
  • TypeScript interface defining the structure of the analytics root content published data (output schema).
    export interface AnalyticsRootContentPublished {
      date: string;
      conteudos: number;
    }
  • src/index.ts:66-71 (registration)
    Registration of the tool in the MCP server using server.tool().
    server.tool(
      getAnalyticsRootContentPublishedTool.name,
      getAnalyticsRootContentPublishedTool.description,
      getAnalyticsRootContentPublishedTool.parameters,
      getAnalyticsRootContentPublishedTool.handler
    );
  • Helper function that performs the actual API fetch to retrieve the analytics root content published data from TabNews.
    export async function getAnalyticsRootContentPublished(): Promise<
      AnalyticsRootContentPublished[]
    > {
      const response = await fetch(
        `${TABNEWS_API_URL}/analytics/root-content-published`
      );
      const data = await response.json();
    
      return data as AnalyticsRootContentPublished[];
    }
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. While it indicates this is a read operation ('get'), it doesn't describe the return format (e.g., structured data, time-series), potential rate limits, authentication needs, or error conditions. The description is minimal and lacks behavioral context.

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 appropriately sized for a no-parameter tool.

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 has 0 parameters, no annotations, and no output schema, the description is minimally complete but lacks depth. It explains what the tool does but doesn't cover behavioral aspects like output format or usage constraints, which are important for an analytics tool even without parameters.

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 with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, but it does imply the tool aggregates data 'per day', which is useful semantic context beyond the empty 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 clearly states the tool's purpose: 'To get how many posts were made (per day) in tabnews'. It specifies the verb ('get'), resource ('posts'), and scope ('per day in tabnews'), though it doesn't explicitly differentiate from sibling tools like 'get analytics child content published' or 'get content'.

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 sibling tools like 'get content' or 'get contents' that might retrieve similar data, nor does it specify prerequisites or exclusions for usage.

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