Skip to main content
Glama
fav-devs

Sociona MCP Server

by fav-devs

get_post_stats

Analyze your social media posts' performance by retrieving key statistics including reach, engagement, and other metrics across connected accounts.

Instructions

Get statistics about your posts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getPostStats() method (lines 305-316) is the handler that calls GET /posts/stats on the API and returns a formatted text response with total, published, failed, and scheduled counts.
    private async getPostStats() {
      const { stats } = await this.apiRequest('GET', '/posts/stats');
    
      return {
        content: [
          {
            type: 'text',
            text: `Post Statistics:\n- Total: ${stats.total}\n- Published: ${stats.published}\n- Failed: ${stats.failed}\n- Scheduled: ${stats.scheduled}`,
          },
        ],
      };
    }
  • The inputSchema definition for 'get_post_stats' tool (no required properties, empty schema).
      name: 'get_post_stats',
      description: 'Get statistics about your posts',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:150-151 (registration)
    The switch-case registration routing 'get_post_stats' to the getPostStats() method.
    case 'get_post_stats':
      return await this.getPostStats();
  • src/index.ts:121-128 (registration)
    The tool name 'get_post_stats' registered in the ListToolsRequestHandler (lines 121-128) with its description and inputSchema.
    {
      name: 'get_post_stats',
      description: 'Get statistics about your posts',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
Behavior2/5

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

With no annotations and minimal description, there is no disclosure of behavioral traits. The tool's side effects or data access patterns are not mentioned, leaving agents uninformed about potential impacts.

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, front-loaded sentence that provides essential information. It is concise but could be expanded slightly to include more detail without becoming verbose.

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 lack of output schema and annotations, the description is adequate but incomplete. It does not specify what statistics are returned, limiting the agent's ability to interpret results accurately.

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 zero parameters, and the description adds no further meaning. Since schema coverage is 100% and there are no parameters to document, the description is sufficient for this context.

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 action ('get') and resource ('statistics about your posts'). It effectively communicates the tool's purpose, distinguishing it from siblings like 'get_posts' which likely returns post content. However, it does not explicitly differentiate from other tools, leaving room for ambiguity.

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 is provided on when to use this tool versus alternatives. The description lacks context for appropriate usage, such as prerequisites or scenarios where this tool is preferred.

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/fav-devs/sociona-mcp-server'

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