ViralDecoder

Get an analysis

get_analysis

Read-onlyIdempotent

Use this when you have a job_id (from analyze_video or my_library) and need the status or the full result of that analysis: hook, hook score, why it went viral, the adapted script, post description (caption), hashtags, transcript. It also gives content_type (video, carousel or thread) and, for a carousel, slide_count and its slide-by-slide breakdown. For a Threads post (content_type thread) the thread block instead: the post's lines with text read from its images, likes and views with the verdict against the author's usual, hook, structure, why it got traction, call to action, what not to copy, a thread of the user's own with three first lines and a reel script; a thread has no transcript or frames. Only the connected account's own analyses are visible. Read-only. Do not use to start a new analysis; analyze_video does that.

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"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only and idempotency, so the 'Read-only' sentence adds little. What the description does add is real behavioral context: visibility is restricted to the connected account's own analyses, and output shape varies by content_type (video/carousel/thread), with threads having no transcript or frames.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The leading use-case sentence is well front-loaded, but the middle is a dense enumeration of every output field, and the thread block list runs long as a single sentence. Much of it earns its place because there is no output schema, yet the middle reads like a field dump rather than structured guidance.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so fairly well, covering the standard analysis payload, carousel slide details and the alternate thread block. It stops short of saying what happens for an in-progress or failed job, which is the main gap for a status-retrieval 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 0% and the schema only says 'Job Id' with no format. The description partly compensates by explaining the parameter's provenance (returned by analyze_video or my_library), but it never says what a job_id looks like or how to know when an analysis is not yet ready.

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?

States a specific verb and resource: retrieve the status or full result of an existing analysis by job_id, and enumerates what comes back (hook, hook score, adapted script, caption, hashtags, transcript). It also distinguishes itself from the analyze_video sibling, which starts a new analysis, so an agent can tell the two apart without opening the schema.

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?

Gives an explicit precondition ('when you have a job_id') and names where that id comes from (analyze_video or my_library). It also states a negative case directly: 'Do not use to start a new analysis; analyze_video does that.'

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

All ViralDecoder 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.

Resources

Need Help?