Skip to main content
Glama
Sign In

InstantClips

by ai.instantclips
OverviewDiscussionsAdmin

Rate a finished video

rate_video
Idempotent

Record the user's own verdict on a finished video they have watched: reaction, and optional issues and comment in their words. Never rate for them, and ask at most once. A second call replaces the rating.

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": {
      "video_request_id": "<video_request_id>",
      "reaction": "<reaction>"
    },
    "name": "rate_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
issuesNoWhat went wrong: the hook or script, voice or audio, the product not shown clearly, pacing and cuts, or a visual glitch.
commentNoThe user's own words, as they said them. Empty clears it.
reactionYes
video_request_idYesThe finished video, from get_video or get_product's videos.

Output Schema

NameRequiredDescriptionDefault
ratingYes
next_stepYes
video_request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes beyond the annotations by stating that a repeat call replaces the prior rating (confirming the replace semantics rather than just idempotency) and by constraining the agent not to fabricate a rating or to nag the user. Rate limits, auth, or response shape are not discussed, but the output schema covers the return side.

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?

Three short sentences, front-loaded with what is recorded, then the agent-facing guardrails. Nothing is redundant and nothing could be cut without losing meaning.

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 four-parameter mutation with a full output schema and annotations covering safety and idempotency, the description supplies the missing behavioral rules (who may rate, how often to ask, replacement behavior). Only the identifier parameter's provenance is left entirely to the schema.

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 75% and the schema already explains issues, comment ('empty clears it'), and video_request_id sourcing. The description restates reaction/issues/comment without adding formats or constraints, so it sits at the baseline rather than compensating for the uncovered video_request_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb (record) plus resource (a verdict on a finished video) and enumerates the payload (reaction, issues, comment). A reader knows exactly what the tool does, though it never contrasts itself with the closest sibling, send_feedback, which also conveys user opinion.

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?

Gives real usage conditions: only the user's own verdict, never on their behalf, ask at most once, and a second call replaces the rating. It stops short of naming an alternative tool or stating a precondition like 'after the video is rendered and watched'.

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

All InstantClips 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