Skip to main content
Glama

SeedViews

Original video files

get_files
Read-only

Lists the original file of every approved or paid video, with its post link and the ad-rights line (12 months from the post date, final video only). Read only.

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": {
      "casting_id": "<casting_id>"
    },
    "name": "get_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
casting_idYesThe casting id that cast returned.
casting_tokenNoThe casting_token that cast returned when it was called without an API key. Not needed with an API key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and 'Read only' merely restates that. It does add genuine business context the annotations cannot convey — the ad-rights window (12 months from post date, final video only) — but says nothing about pagination, volume, or errors on a listing call.

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?

A single front-loaded sentence with the resource and returned fields first, then the licensing qualifier, then a two-word safety tag. Nothing is wasted and no clause is filler.

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 only two parameters and no output schema, the description usefully compensates by enumerating what each record contains (file, post link, ad-rights line). Only the absence of result-volume or pagination expectations keeps it from being fully complete.

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% and both parameters are documented in the schema, including the conditional note that casting_token is unneeded with an API key. The description adds no parameter detail, but the schema already carries that burden, so the baseline holds.

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?

Specific verb plus resource: 'Lists the original file of every approved or paid video,' and it names what comes back (post link, ad-rights line). That scope distinguishes it from siblings like check_video or get_results, though it never explicitly contrasts itself with them.

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 by the 'approved or paid video' qualifier — an agent can infer this is the retrieval step after approval or payment, but there is no explicit when-to-use statement, no prerequisites, and no named alternative for other file or status queries.

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