Skip to main content
Glama

SocialGPT

by io.github.scrollmark
OverviewDiscussionsAdmin

Your content profile

get_content_profile
Read-only

Get the caller's OWN content profile / DNA (topics, pillars, voice) synthesized from their content. Scoped per account group (brand): pass a group_id from list_accounts, or omit it for the default group. There is no per-creator content-profile tool — for competitor analysis use get_creator + list_creator_videos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idNoOptional account-group (brand) id from list_accounts. Omit to use the default group.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoPresent only when content_profile is null — why it is null.
content_profileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / group_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional account-group (brand) id from list_accounts. Omit to use the default group."
+}
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / description
      Added value: +"Output of `get_content_profile`. When `content_profile` is null,\n`reason` says why: 'not_connected' (no accounts/onboarding yet) or\n'not_synthesized' (connected but DNA not generated yet)."
    • addedOutput schema / properties
      Added value: +{
+  "content_profile": {
+    "anyOf": [
+      {
+        "description": "The caller's content DNA — empirical persona + prescriptive playbook.",
+        "properties": {
+          "persona": {
+            "default": null,
+            "title": "Persona"
+          },
+          "playbook": {
+            "default": null,
+            "title": "Playbook"
+          }
+        },
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "reason": {
+    "anyOf": [
+      {
+        "enum": [
+          "not_synthesized",
+          "not_connected"
+        ],
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Present only when content_profile is null — why it is null."
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "content_profile"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds context about scoping and that the profile is synthesized from content. No contradictions. Some additional behavioral context beyond annotations is provided, but the core safety trait is already covered.

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?

Three sentences, each serving a distinct purpose: purpose, parameter usage, and alternatives. No unnecessary words. Highly efficient.

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 tool's simplicity (1 optional param, no required, output schema present), the description fully covers purpose, usage, and alternatives. No gaps.

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?

The single parameter group_id is fully described in the schema (100% coverage). The description repeats the schema's guidance about omitting for default or passing from list_accounts, adding no new meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 states 'Get the caller's OWN content profile / DNA (topics, pillars, voice) synthesized from their content', providing a specific verb and resource. It distinguishes from competitor analysis tools by noting there is no per-creator tool.

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

Usage Guidelines5/5

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

Explicitly says when to use (caller's own profile, per account group) and when not to use ('For competitor analysis use get_creator + list_creator_videos'), offering clear alternatives.

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