Skip to main content
Glama
fav-devs

Sociona MCP Server

by fav-devs

get_accounts

Get a complete list of social media accounts linked to your Sociona server, simplifying account management and cross-platform posting.

Instructions

Get list of connected social media accounts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getAccounts() method that executes the tool logic. It calls the API endpoint GET /accounts, handles the empty case, and formats the account list for the response.
    private async getAccounts() {
      const { accounts } = await this.apiRequest('GET', '/accounts');
    
      if (!accounts || accounts.length === 0) {
        return {
          content: [
            {
              type: 'text',
              text: 'No social media accounts connected.',
            },
          ],
        };
      }
    
      const accountList = accounts
        .map((a: any) => `- ${a.provider}: ${a.handle} (${a.status})`)
        .join('\n');
    
      return {
        content: [
          {
            type: 'text',
            text: `Connected accounts:\n${accountList}`,
          },
        ],
      };
    }
  • Tool registration with name 'get_accounts', description, and inputSchema (empty object since it takes no parameters).
    {
      name: 'get_accounts',
      description: 'Get list of connected social media accounts',
      inputSchema: {
        type: 'object',
        properties: {},
      },
  • src/index.ts:132-167 (registration)
    The CallToolRequestSchema handler that routes 'get_accounts' to the getAccounts() method.
    // Handle tool calls
    this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        switch (name) {
          case 'publish_post':
            return await this.publishPost(args);
          case 'schedule_post':
            return await this.schedulePost(args);
          case 'get_accounts':
            return await this.getAccounts();
          case 'get_posts':
            return await this.getPosts(args);
          case 'get_scheduled_posts':
            return await this.getScheduledPosts(args);
          case 'cancel_scheduled_post':
            return await this.cancelScheduledPost(args);
          case 'get_post_stats':
            return await this.getPostStats();
          default:
            throw new Error(`Unknown tool: ${name}`);
        }
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return {
          content: [
            {
              type: 'text',
              text: `Error: ${errorMessage}`,
            },
          ],
          isError: true,
        };
      }
    });
Behavior1/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the tool gets a list but omits critical details such as whether results are paginated, authentication requirements, rate limits, or what constitutes 'connected accounts'.

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 that front-loads the core action and resource. Every word contributes meaning, with no redundancy or filler.

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?

While the tool is simple (no parameters, no output schema), the description does not specify what information is returned per account (e.g., IDs, names, platforms). This lack of output context could leave the agent uncertain about the response format.

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 with 100% coverage, so the description does not need to explain parameters. The baseline for no parameters is 4, and the description sufficiently conveys the tool's purpose without param ambiguity.

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 'Get list of connected social media accounts' clearly states the verb (Get) and resource (list of connected social media accounts), distinguishing it from sibling tools like get_posts or publish_post which deal with different resources or actions.

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 like get_posts or get_post_stats. The description does not specify context, prerequisites, or exclusions, leaving the agent to infer usage without explicit differentiation.

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