oriiion

Create From Trend

create_from_trend

Turn one trend from find_trends_for_business into content for the user: a single post (their own image, never the creator's clip), a short video script they film on their phone via a teleprompter link, or an Instagram carousel. Same pipeline as creating from a shared link. Pass the tailored hook and idea from find_trends_for_business to keep the angle.

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": {
      "trendId": "<trendId>",
      "format": "<format>"
    },
    "name": "create_from_trend"
  }
}

Input Schema

Name	Required	Description
`hook`	No	The tailored hook from find_trends_for_business
`idea`	No	The tailored content idea from find_trends_for_business
`format`	Yes	post = one social post, script = phone-filmed video with teleprompter, carousel = Instagram slide deck, reel = (audio trends only) product photos cut to the trending sound, no camera
`context`	No	Anything the user added, e.g. a product to feature
`trendId`	Yes	trendId from find_trends_for_business
`platform`	No	Post only: which platform to write for (default facebook)
`mediaUrls`	No	reel only: 2-20 image URLs to cut to the sound, instead of productIds
`productIds`	No	reel only: product ids from list_products (e.g. ['feed-17']) whose photos are cut to the sound
`scheduledFor`	No	ISO date to schedule the post or carousel for

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With readOnlyHint=false already flagging a write/mutation, the description adds real behavioral context: the post uses the user's own image and never the creator's clip, the script is filmed on the phone via a teleprompter link, and it shares the create-from-link pipeline. It does not mention async generation or what the call returns, but the added traits go meaningfully beyond the annotations.

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?

Three sentences, front-loaded with the core action and formats. Every clause is useful (source sibling, format outputs, pipeline equivalence, param guidance), though the parenthetical image caveat and pipeline note add slight length without new decision-relevant content.

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?

For a 9-parameter mutation with no output schema, the description covers the source, outputs, and params sufficiently for correct selection and invocation. It stops short of describing the return value or asynchronous generation behavior, which an agent might want when this is one of many generate_* tools.

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 100%, so the baseline is 3, but the description adds intent beyond the schema by explaining that hook and idea from find_trends_for_business should be passed 'to keep the angle'. Its format enumeration is incomplete (omits reel), which the schema covers, so the lift is real but modest.

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+resource (turn one trend into content) and enumerates the concrete outputs: post, phone-filmed video script, or Instagram carousel. It explicitly ties the input to the sibling find_trends_for_business, so an agent can tell it apart from that listing tool and from create_from_link 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: it is used after find_trends_for_business and consumes that tool's hook/idea. It notes 'Same pipeline as creating from a shared link' but never says when to prefer this tool over create_from_link or the other content-creation siblings, and there are no exclusions.

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

All oriiion 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?