Skip to main content
Glama

Get long-form project

get_project
Read-only

Scenes (each with its script), takes (status, length, tracks), the take each scene uses and the finished length so far, and each graphic: its status (ready, rendering, failed, waiting, or hidden with the reason), its start and end in seconds in the finished video, and its render's task_id; and each still image: its status, start and end, placement, the words it is pinned to, where its image came from and any full-frame graphic covering it.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom create_project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

readOnlyHint=true already establishes this is a safe read. The description adds genuine behavioral value beyond that by revealing that statuses (rendering, failed, waiting) and a render task_id are returned, implying the tool doubles as a progress-polling surface. It does not state pagination, size limits, or error behavior for an invalid project_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The entire description is a single run-on sentence chained with 'and', listing return fields with no front-loaded statement of what the tool does. It is dense and hard to scan, and the key fact (this returns a project's full state) is buried in the enumeration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, describing return values is legitimately the description's job, and it does so in detail. However, it omits framing about what the tool is for and how it relates to get_render/get_transcript, so the agent must infer the calling context entirely from the field list.

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 the single parameter project_id already carries a description ('From create_project'), so the schema does the heavy lifting. The prose adds nothing about project_id semantics, though with one fully documented parameter the baseline of 3 applies.

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 description enumerates the specific resource contents (scenes with scripts, takes with status/length/tracks, graphics with status and timing, still images with placement) so an agent knows this returns the full state of one long-form project. It never names the verb or distinguishes itself from siblings like get_render, get_task or get_transcript, leaving the agent to infer that this is the project-level read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_render or get_transcript for narrower reads. The only implied usage is that this is the way to inspect a project, which the agent must deduce from the field list.

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