SocialGPT

Analysis job status

get_analysis_status

Read-only

Check the status of an analyze_creator (or analyze_post creator-backfill) job by job_id. Note: this tracks the creator-ingest job, not a single post's video analysis. To know when one post is ready, poll get_video_analysis(platform, post_id) — it returns {"status": "pending"} until ready.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_analysis_status"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes	The job_id (a UUID) returned by analyze_creator or analyze_post.

Output Schema

Name	Required	Description
`note`	Yes
`error`	Yes
`job_id`	Yes
`result`	No
`status`	Yes	One of: pending, scraping, completed, failed.
`platform`	Yes
`progress`	Yes	Completion percentage (0-100).
`username`	Yes
`creator_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 24, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"Output of `get_analysis_status` — a creator-ingest job's progress."

addedOutput schema / properties

Added value: +{
+  "creator_id": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "error": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "job_id": {
+    "type": "string"
+  },
+  "note": {
+    "type": "string"
+  },
+  "platform": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "progress": {
+    "description": "Completion percentage (0-100).",
+    "type": "integer"
+  },
+  "result": {
+    "default": null,
+    "title": "Result"
+  },
+  "status": {
+    "description": "One of: pending, scraping, completed, failed.",
+    "type": "string"
+  },
+  "username": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  }
+}

addedOutput schema / required

Added value: +[
+  "job_id",
+  "status",
+  "progress",
+  "creator_id",
+  "platform",
+  "username",
+  "error",
+  "note"
+]

Changed1 schema field changedJun 24, 2026
- addedInput schema / properties / job_id / description
```
Added value: +"The job_id (a UUID) returned by analyze_creator or analyze_post."
```
First observedJun 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true, and the description adds behavioral context by explaining that this tool tracks the creator-ingest job, not individual post analysis. It does not contradict annotations. It could mention response format or polling behavior, but the existing description is strong.

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 pack essential information: what the tool does, what it does not track, and the correct alternative. Every sentence is necessary and well-structured.

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 status-check tool with one parameter and an output schema (implied), the description covers the essential behavioral distinction against sibling tools. It is complete and requires no additional elaboration.

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 clear description of the job_id parameter: 'The job_id (a UUID) returned by analyze_creator or analyze_post.' The description adds minimal extra meaning beyond the schema, re-iterating the source of the job_id. Baseline 3 is appropriate as the schema already does the heavy lifting.

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 explicitly states 'Check the status of an analyze_creator (or analyze_post creator-backfill) job by job_id', using a specific verb and resource. It clearly distinguishes from sibling tool get_video_analysis by noting it tracks the creator-ingest job, not a single post's video analysis.

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?

The description provides explicit guidance on when to use this tool vs. the alternative: 'To know when one post is ready, poll get_video_analysis(platform, post_id) — it returns {"status": "pending"} until ready.' This clearly states when not to use this tool and names the sibling tool to use instead.

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

All SocialGPT tools Inspect

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.