Skip to main content
Glama
Sign In

HypeFox

by app.hypefox
OverviewDiscussionsAdmin

Change a slot's idea and remake its video now

change_slot_idea
Destructive

Changes the idea of a post in the calendar (Automatic or Manual) and starts its new video right away: for example the user doesn't like the video planned at 16:05 and wants a sales video there. Costs 10 credits (Paper Collage 20), like making a video. The slot keeps its time; the old video, if it was ready, goes to the reserve (HypeFox uses it later for a slot of the same kind) and its scheduled posts for this slot are withdrawn. Set sales: true to turn it into a sales video (accounts that sell; with DM sales it needs a keyword), sales: false to turn a sales slot into a normal one. A slot to film becomes an AI video. Not for slots that go out within the hour, are already out, or whose video is being made. Show the user what changes (and that it changes this week's 70-20-10 mix if the role changes) and act only on their explicit yes.

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": {
      "slot_id": "<slot_id>",
      "idea": "<idea>"
    },
    "name": "change_slot_idea"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyNoWhy this post changed, shown to the user in the calendar: in their app language, speaking to them (e.g. in English «You asked for a sales video here», in Italian «Hai chiesto un video di vendita qui»)
ideaYesThe new topic of the video, in the language of the videos
angleNoHow to tell it: the angle, the promise, what to show
factsNoReal facts, numbers or story from the user that the video must use
salesNotrue = make it a sales video; false = a normal one; leave out to keep the slot's kind
keywordNoSales videos that end in DMs: the keyword people send, 3-12 letters or digits. Default: the project's keyword (sells.keyword)
slot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / why / description
      Previous value: -"Why this post changed, shown to the user in the calendar: in their app language, speaking to them (e.g. «Hai chiesto un video di vendita qui»)"New value: +"Why this post changed, shown to the user in the calendar: in their app language, speaking to them (e.g. in English «You asked for a sales video here», in Italian «Hai chiesto un video di vendita qui»)"
  2. Changed1 schema field changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Sales videos that end in DMs: the keyword people send, 3-12 letters or digits"New value: +"Sales videos that end in DMs: the keyword people send, 3-12 letters or digits. Default: the project's keyword (sells.keyword)"
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the cost (10 credits, 20 for Paper Collage), that the old video goes to reserve, that scheduled posts for the slot are withdrawn, and that the slot keeps its time. This substantially clarifies the destructive and non-idempotent behavior already hinted at by destructiveHint=true and idempotentHint=false.

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 description is a dense single paragraph, but it is front-loaded with the purpose, cost, and main side effects. The operational details are relevant, though the paragraph is packed enough that readability could be improved.

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?

For a destructive, credit-consuming mutation with no output schema, the description covers the important contexts an agent needs: cost, side effects, slot preservation, what happens to the old video, excluded slot states, sales-mode behavior, and confirmation requirements.

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 high at 86%, so the schema already documents most parameters. The description adds useful meaning for the `sales` flag, including the distinction between ordinary and sales accounts and the DM keyword requirement, though it does not add much beyond the schema for `why`, `angle`, or `facts`.

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 uses a specific verb and resource: changing a calendar post's idea and immediately remaking its video. It clearly separates this from merely editing a slot by explaining that the old video is withdrawn to reserve and a new one starts right away.

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?

It gives a concrete use scenario (the user does not like the video planned at 16:05 and wants a sales video there) and explicit exclusions: not for slots within the hour, already published, or currently rendering. It also requires showing the user what changes and acting only after an explicit yes.

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

All HypeFox toolsInspect
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