Skip to main content
Glama

CreatorsCompanion

Get viral results

get_viral_results
Read-only

Returns the posts of a find_viral_posts search by job_id, or of the latest search when job_id is left out. Use it to check on a search that was still running. Returns posts[] with post_key, for get_transcript, save_inspiration and generate_content remix. viral_score: views against followers, weighted by audience size; 18 or more is an outlier. Uses no credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_viral_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNoThe job_id from find_viral_posts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds non-annotation behavior worth knowing: it falls back to the latest search when job_id is omitted, it costs no credits, and it describes the resulting posts[] shape and viral_score calculation.

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

Conciseness4/5

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

The definition is dense and front-loaded: purpose first, then the fallback rule, then return shape and scoring semantics. The clause 'Returns posts[] with post_key, for get_transcript, save_inspiration and generate_content remix' is compressed to the point of mild ambiguity, but no sentence is wasted.

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 burden of explaining returns and does so, including the viral_score scale and the 18-point outlier threshold. It is silent on pagination or result-capping behavior, which matters given a load_more_viral sibling exists.

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%, so the job_id field is already documented as coming from find_viral_posts, giving a baseline of 3. The description does add one piece of meaning beyond the schema — that omitting job_id returns the latest search — but gives no detail on identifier format or errors for an unknown job_id.

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 opens with a specific verb and resource ('Returns the posts of a find_viral_posts search') and explicitly ties itself to the sibling that produces the job_id, so an agent can distinguish it from find_viral_posts and load_more_viral immediately.

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?

It states a clear use case ('Use it to check on a search that was still running') and names downstream tools that consume the returned post_key (get_transcript, save_inspiration, generate_content). It does not explicitly say when not to use it versus load_more_viral, which is the closest ambiguity.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.