Skip to main content
Glama
dinwal
by dinwal

social_account_list

Retrieve connected social media accounts and their IDs to manage posting workflows and content scheduling.

Instructions

List all connected social media accounts with their IDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration and handler implementation for the 'social_account_list' tool, which calls the corresponding RecurPost API endpoint.
    // 3. List connected social accounts
    server.tool(
      "social_account_list",
      "List all connected social media accounts with their IDs",
      {},
      async () => {
        try {
          return toolResult(await callAPI("/api/social_account_list"));
        } catch (e) {
          return toolResult({ error: String(e) }, true);
        }
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It adds valuable behavioral context by specifying 'connected' (implying prior authorization is required) and 'with their IDs' (indicating the return payload includes identifiers). However, it lacks details on pagination, error conditions, or output structure that annotations would typically cover.

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 with no redundant words. It front-loads the action verb and immediately follows with the resource and return value details.

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 low complexity (zero parameters, no nested objects) and absence of an output schema, the description adequately covers the basic operation by mentioning the returned IDs. However, it could improve by describing the return structure (array vs object) or what constitutes a 'connected' account state.

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?

With zero parameters, the baseline score is appropriately set to 4. The description does not need to compensate for missing schema documentation since the empty input schema is self-explanatory.

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 provides a clear verb ('List') and resource ('connected social media accounts'), and specifies the key returned field ('IDs'). It implicitly distinguishes from sibling 'connect_social_account_urls' (which adds connections) and 'library_list' (which lists different content), though it could explicitly contrast these.

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, prerequisites (e.g., requiring prior authentication), or when not to use it (e.g., if looking for unconnected accounts).

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/dinwal/recurpost-mcp'

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