Skip to main content
Glama

XCut AI – Viral Content Research

Find a profile's outlier posts

xcut_find_outliers
Idempotent

Use this when the user asks which of a creator's, competitor's or their own posts performed best or beat the account's normal, or what works for an account before writing. Scores the latest 20, 30, 50 or 100 posts against that account's own median and says by how much each beat it. About 3-4 credits for 30 posts on Instagram or TikTok, none on YouTube, more on Facebook. Longer runs return a job_id for xcut_get_job. Do not use for a full metrics table (use xcut_profile_analytics) or for a topic across many accounts (use xcut_search_viral).

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": {
      "profile": "<profile>",
      "platform": "<platform>"
    },
    "name": "xcut_find_outliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
postsNoHow many recent posts to analyse: 20, 30, 50 or 100. Default 30.
profileYesProfile link or @handle.
platformYesinstagram, tiktok, youtube or facebook.
canvas_idNoCanvas (UUID) that owns the thumbnails. Optional. The results are returned here, not placed on the canvas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / canvas_id / description
      Previous value: -"Also save the results to this canvas (UUID). Optional."New value: +"Canvas (UUID) that owns the thumbnails. Optional. The results are returned here, not placed on the canvas."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing credit costs (3-4 for 30 posts on Instagram/TikTok, none on YouTube, more on Facebook), the asynchronous job_id behavior for longer runs and the follow-up tool (xcut_get_job), and the non-obvious canvas_id side effect ('results are returned here, not placed on the canvas'). No contradiction with readOnlyHint=false, idempotentHint=true, or destructiveHint=false.

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?

Four tight sentences: purpose and trigger first, then scoring behavior, then cost and async behavior, then exclusions. Every sentence carries non-redundant information an agent needs to decide or call correctly.

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?

Despite no output schema, the description conveys what the result looks like ('says by how much each beat it'), the cost side, the async/job_id path, and the canvas side effect. For a four-parameter read-style analysis tool with openWorld and idempotent annotations, this is complete enough to invoke confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so baseline is 3. The description adds value by tying the posts enum to a cost model and by clarifying that canvas_id only supplies thumbnails and does not receive results, a nuance the schema's 'Canvas that owns the thumbnails' does not fully convey. It does not add syntax detail for profile or platform, but those are adequately covered in-schema.

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 ('Find a profile's outlier posts') and immediately explains the mechanism: scoring the latest 20-100 posts against the account's own median and reporting the margin. It also names the exact sibling tools it is not (xcut_profile_analytics, xcut_search_viral), so an agent can disambiguate without opening a 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?

Explicit when-to-use ('when the user asks which of a creator's, competitor's or their own posts performed best... or what works for an account before writing') plus two explicit when-not-to-use cases with the correct alternative named for each. Nothing is left to inference.

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.

Resources