Skip to main content
Glama

SendIt

by io.github.Shree-git

List Connected Accounts

list_connected_accounts
Read-onlyIdempotent

List all connected social media accounts. Pass team_id to see a team's accounts instead of your personal ones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_idNoTeam ID to list team accounts. Get available teams with list_teams. If omitted, lists personal accounts.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
isErrorNo
accountsNo
errorMessageNo
connectedCountNo
totalPlatformsNo
followUpSuggestionsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "accounts": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "authUrl": {
+            "type": "string"
+          },
+          "connected": {
+            "type": "boolean"
+          },
+          "expiryWarning": {
+            "type": "boolean"
+          },
+          "platform": {
+            "enum": [
+              "x",
+              "linkedin",
+              "linkedin-page",
+              "facebook",
+              "instagram",
+              "threads",
+              "bluesky",
+              "mastodon",
+              "nostr",
+              "youtube",
+              "tiktok",
+              "lemmy",
+              "discord",
+              "slack",
+              "telegram",
+              "pinterest",
+              "dribbble",
+              "devto",
+              "hashnode",
+              "gmb",
+              "whop",
+              "producthunt"
+            ],
+            "type": "string"
+          },
+          "platformUsername": {
+            "type": "string"
+          },
+          "username": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "connectedCount": {
+      "type": "number"
+    },
+    "errorMessage": {
+      "type": "string"
+    },
+    "followUpSuggestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "isError": {
+      "type": "boolean"
+    },
+    "totalPlatforms": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds behavioral context beyond annotations by explaining the personal vs. team scope, which is not captured in the annotations. It does not discuss pagination or return format, but the output schema covers that.

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 two concise sentences, with the primary purpose first and the parameter behavior second. Every word adds value, and there is no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one optional parameter, the description, combined with complete schema annotations and an output schema, provides enough context for an agent to understand the tool's scope and behavior. No significant gaps remain.

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

Parameters3/5

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

Schema description coverage is 100%, with the team_id parameter already thoroughly documented ('Team ID to list team accounts. Get available teams with list_teams. If omitted, lists personal accounts.'). The description essentially repeats this information, adding marginal value beyond the schema.

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 clearly states the tool's function with a specific verb ('List') and resource ('connected social media accounts'), and it distinguishes from sibling tools by focusing on social media accounts rather than connectors or other resources. The team_id parameter adds a scope distinction that further clarifies the purpose.

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

Usage Guidelines4/5

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

The description provides clear guidance on when to use the optional team_id parameter ('Pass team_id to see a team's accounts instead of your personal ones'). It does not explicitly mention alternatives or exclusions, but the usage context is clear for a simple listing tool.

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

All SendIt toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3/5.0
Disambiguation2/5

With 148 tools, there is significant overlap. For example, generate_content, publish_ai, generate_post_bundle, and request_project_content all generate content; get_analytics, get_unified_analytics, get_post_analytics, get_ad_performance, and get_unified_ad_report all fetch performance metrics; and list_inbox vs list_conversations blur comment and conversation management. Descriptions help, but boundaries between tools are often unclear.

Naming Consistency3/5

Most tools follow a verb_noun pattern (e.g., list_teams, create_goal, delete_post), but there are notable deviations: create_library_item vs save_to_library, publish_content vs publish_ai, schedule_content vs schedule_content_advanced, and connect_platform vs connect_connector. Mixed prefixes like 'autopilot_', 'check_', and 'get_' are fine, but overlapping verbs and a hyphen in 'connect_linkedin-page' reduce consistency.

Tool Count1/5

148 tools is extreme for any server. Even for a broad social media management platform, this is far beyond what an agent can effectively navigate. The count is unwieldy and suggests the surface should be split into multiple focused servers (publishing, analytics, connectors, workflows, etc.).

Completeness3/5

The core social publishing workflow is well covered (create, schedule, publish, edit, delete, retry), and there are extensive features for analytics, workflows, connectors, and AI agents. However, some resources have CRUD gaps: no update/delete for brand voices, no delete_project, no update/delete for Product Hunt goals, and no explicit get_workflow. These are workable but notable omissions.

Resources