Skip to main content
Glama

SocialGPT

by io.github.scrollmark
OverviewDiscussionsAdmin

Get a connected account

get_account
Read-only

Get one of the caller's connected accounts by id (from list_accounts). 404s if the id isn't one of your connected accounts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYesAn account_id from list_accounts.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYes
usernameYes
account_idYes
is_verifiedNo
display_nameNo
profile_linkNo
account_group_idNo
account_group_nameNo
profile_picture_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / description
      Added value: +"One of the caller's connected social accounts. `account_id` is the handle\nother tools accept (e.g. get_account_metrics, list_videos)."
    • addedOutput schema / properties
      Added value: +{
+  "account_group_id": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "account_group_name": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "account_id": {
+    "type": "string"
+  },
+  "display_name": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "is_verified": {
+    "default": false,
+    "type": "boolean"
+  },
+  "platform": {
+    "type": "string"
+  },
+  "profile_link": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "profile_picture_url": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "username": {
+    "type": "string"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "account_id",
+  "platform",
+  "username"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / account_id / description
      Added value: +"An account_id from list_accounts."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true and openWorldHint=false. The description adds that the tool 404s on invalid ids, a behavioral detail not in annotations. It also specifies 'caller's connected accounts', providing context.

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?

Two sentences, no redundancy, front-loaded with key information. Highly concise.

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?

Given the presence of an output schema, the description sufficiently covers the tool's behavior: retrieval, id source, error case, and ownership context. No gaps for a simple get tool.

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 coverage is 100% with a description for account_id. The description reiterates the source (from list_accounts) but adds little 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 'Get' as the verb and specifies the resource as 'connected accounts by id'. It explicitly ties the id to list_accounts, distinguishing it from sibling tools like list_accounts.

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 indicates the id should come from list_accounts, implying usage after listing. It mentions 404 for invalid ids, but does not explicitly list alternatives or when to use other tools.

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

All SocialGPT toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources