Skip to main content
Glama
Sign In
@fopost/mcp

@fopost/mcp

Official
by fopost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_accounts

Retrieve all social accounts connected to a workspace, showing platform, username, primary flag, and connection status for each.

Instructions

List connected social accounts in a workspace. Returns platform, username, primary flag, and connection status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>"
    },
    "name": "list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

The description discloses return fields (platform, username, primary flag, connection status), which adds context beyond the input schema. However, without annotations, it omits details like authentication requirements, rate limits, and the meaning of 'connected' or 'primary flag'. It is helpful but not exhaustive.

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?

A single, well-structured sentence that efficiently states the action and lists return fields. No redundant words; all information is presented clearly.

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?

For a simple list operation, the description is mostly sufficient, but it omits potential nuances like pagination, ordering, or error handling. The contrast with get_account_health is not clarified, which could lead to confusion in the absence of an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema_description_coverage at 0%, the description does not mention workspace_id or any parameter details. Although the parameter name is intuitive, the description fails to reinforce its requirement or clarify the expected format beyond what the schema provides.

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 uses a clear verb 'list' and specifies the resource 'connected social accounts in a workspace', distinguishing it from siblings like list_posts and list_workspaces. It immediately conveys what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage is implied through the purpose, but the description does not explicitly state when to use this tool over alternatives or mention any exclusions. No contrast with get_account_health or other account-related tools is provided, leaving selection inference to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools