Skip to main content
Glama
Sign In

FrameThrower

by ai.framethrower
OverviewDiscussionsAdmin

get_commercial

Read-only

The full breakdown of one commercial by id: idea, logline, tagline, product, audience, every credit by role (director, agency, production company, DP, editor, music, post, sound, VFX), every award (show, year, level, category), craft numbers (shots, average shot length, cuts per minute, when the product / brand / emotional peak / end card land), the script with timings, and the shot list (caption, tags and still per shot; with clips: true, each shot's clip too).

Input Schema

NameRequiredDescriptionDefault
idYesCommercial id, e.g. AD-0505
clipsNotrue = also return a short clip of each shot (the call costs 8 credits instead of 2). Ask only when the user wants to see the shots move.
shotsNoInclude the shot list (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / clips
      Added value: +{
+  "description": "true = also return a short clip of each shot (the call costs 8 credits instead of 2). Ask only when the user wants to see the shots move.",
+  "type": "boolean"
+}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds real value by itemizing exactly what payload comes back (credits by role, awards, craft numbers, script timings, shot list) since there is no output schema. It omits the credit cost of clips: true (8 vs 2), though the schema parameter description covers that.

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?

A single front-loaded sentence that opens with the resource and scope, then enumerates fields. The dense mid-sentence list of credits and craft metrics is long but every item conveys distinct content an agent could not get from the schema.

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?

With no output schema, the description carries the full burden of describing the return value and does so thoroughly, and all three parameters are documented at 100% coverage in the schema. Minor gap: the clips credit cost and pagination/size expectations are not mentioned in the description itself.

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 description coverage is 100% and the schema already explains id format (AD-0505), the clips cost tradeoff, and the default for shots. The description only restates clips behavior ('with clips: true, each shot's clip too'), adding nothing the schema does not already say.

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?

The definition gives a specific verb+resource ('The full breakdown of one commercial by id') and then enumerates the returned content, so its role as the single-record detail tool is unmistakable versus the search_* siblings. It stops short of explicitly naming any sibling tool, so the distinction is inferred from content breadth rather than stated.

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 only implied: the phrase 'full breakdown of one commercial by id' signals the drill-down case after a search, and 'with clips: true, each shot's clip too' hints at the optional branch. Nothing states when to prefer this over commercials_profile or find_similar, and there are no exclusions or prerequisites.

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

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