XCut AI – Viral Content Research

Check a job

xcut_get_job

Idempotent

Use this when another XcutAI tool returned a job_id: it returns status running with a suggested wait, or the finished result (outlier analysis, profile analytics, imports with their transcript, agent replies). Free. Do not use without a job_id from an XcutAI tool.

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

Input Schema

Name	Required	Description	Default
`job_id`	Yes	The `job_id` an XcutAI tool returned, unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026
- changedInput schema / properties / job_id / minLength
```
Previous value: -10New value: +1
```
First observedOct 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With annotations present, the description still adds real context: cost ('Free'), the polling contract (status 'running' plus a suggested wait), and the shape of a finished payload. It does not explain what readOnlyHint=false implies (i.e. whether fetching consumes or mutates the job), which is the one behavioral gap left.

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 dense sentences, front-loaded with the trigger condition and the outcome contract, with no filler. Every clause carries information an agent needs before calling.

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?

No output schema exists, and the description compensates by enumerating the possible return states and their meanings. It leaves the polling cadence and job-expiry behavior implicit, but for a one-parameter read-and-check tool this is largely complete.

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% and the single parameter already documents that the job_id must be the one an XcutAI tool returned, unchanged. The description reinforces the provenance but adds no syntax, format, or example beyond what the schema already carries.

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 ('check a job' via job_id) and immediately names the entry condition plus the two possible outcomes ('running' with a suggested wait, or the finished result with concrete result types). An agent can distinguish it from every sibling because it is the sole polling/retrieval companion to the async tools.

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?

Both the when ('use this when another XcutAI tool returned a job_id') and the when-not ('Do not use without a job_id from an XcutAI tool') are stated explicitly. No alternative tool exists for this purpose, so no alternative needs to be named.

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

All XCut AI – Viral Content Research 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?