Skip to main content
Glama

SeedViews

Results of a casting

get_results
Read-only

Reads the casting: status, the opening message, each creator and their state (found, contacted, replied, signed, filming, posted, checked, paid, passed) with our first message to them, each video with views and cost per 1,000 views, totals, and needs_person (what a human must do next, if anything). Read only. Results take days, not minutes: check once a day, do not poll. When needs_person names a deadline (a checked video counts as approved 48 hours after its check), act that same day, or set notify_url to be told.

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_results"
  }
}

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.9/5.0
Behavior3/5

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

"Read only" simply restates readOnlyHint=true, so no credit there. Beyond annotations it does add real behavior: results mature over days so polling is discouraged, and a checked video counts as approved 48 hours after its check, which is a consequential deadline rule an agent cannot infer from the schema. With the safety profile already covered by annotations, this additional context earns a 3 rather than higher.

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?

Front-loads the core framing ("Reads the casting") and packs the return inventory into one sentence, then follows with actionable constraints. It is dense but every clause carries information; the long enumerated first sentence is the only mild readability cost.

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?

No output schema exists, and the description compensates by itemizing the returned fields, including the needs_person signal and the state vocabulary. The 48-hour approval deadline and the poll-once-a-day cadence round out what an agent needs to act correctly; only edge cases such as what happens for an unknown or unauthorized casting_id are unaddressed.

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 100% and both parameters carry their own descriptions, including when casting_token is unnecessary. The description adds nothing about casting_id or casting_token; its mention of notify_url refers to a setting not present in this tool's schema, so it does not clarify parameters here. Baseline 3 applies.

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 ("Reads") and resource ("the casting") and then enumerates exactly what is returned: status, opening message, per-creator state from a named state vocabulary, per-video views and cost per 1,000 views, totals, and needs_person. That enumeration makes it unmistakable against siblings like get_files or pay_creator, which operate on different resources or mutate state.

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 explicit operational guidance: "check once a day, do not poll" and "act that same day, or set notify_url to be told," which sets a clear when-to-use and when-not-to-poll rule with a named alternative (notify_url). It stops short of routing the agent away from a specific sibling tool, so it is clear context rather than full alternative selection.

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