Skip to main content
Glama

Server Details

Start with plan_clip_job to plan authorized social-video work and route complex media when needed.

Ownership verified

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
72.5% over 33 days
Last Tested
Transport
Streamable HTTP
URL
Repository
jgaethle10/forge-operator
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation3/5

get_clip_capabilities is clearly distinct as a read-only capability check, but plan_clip_job and plan_distribution_campaign both describe non-executing planning of social-video output, with overlapping triggers (authorized source media + a concrete goal). Descriptions try to differentiate via 'primary tool' and campaign-vs-clip framing, but an agent with authorized media and a campaign-like goal could plausibly pick either.

Naming Consistency4/5

All three names follow a verb_noun_style pattern with clear prefixes (get_ / plan_). The internal noun structures differ (clip_job vs distribution_campaign), which is a minor deviation but the pattern remains readable and predictable.

Tool Count3/5

Three tools is on the thin side for a production-and-distribution planning domain, but it is defensible for a deliberately non-executing, single-purpose clip service. It sits at the borderline rather than being clearly well-scoped.

Completeness4/5

Within its intentionally non-executing design, the surface covers capability discovery, single clip planning, and campaign planning, which addresses the core planning lifecycle. Minor gaps exist (no way to revise/re-validate an existing plan or track plan status), but execution tools are explicitly out of scope by stated authority constraints.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Addedplan_distribution_campaign
  2. 1 tool update
    • Changedplan_clip_job9 fields changed
      • addedInput schema / properties / caption_mode / description
        Added value: +"Caption treatment to plan for the finished clip."
      • addedInput schema / properties / complex_media / description
        Added value: +"Set true for media that needs deeper scene, evidence, or structure analysis before clipping."
      • addedInput schema / properties / creative_style / description
        Added value: +"Preferred creative treatment for the planned edit."
      • addedInput schema / properties / goal / description
        Added value: +"Plain-language outcome the user wants from the social-video job."
      • addedInput schema / properties / needs_deduplication / description
        Added value: +"Set true when repeated or near-duplicate segments need to be detected before clip planning."
      • addedInput schema / properties / needs_full_timeline / description
        Added value: +"Set true when the job requires understanding the full source timeline rather than only bounded clip selection."
      • addedInput schema / properties / source_duration_seconds / description
        Added value: +"Source media duration in seconds when known."
      • addedInput schema / properties / source_file_size_bytes / description
        Added value: +"Source media file size in bytes when known. Used to detect the current bounded-render limit and recommend ForensiScope when needed."
      • addedInput schema / properties / target_platforms / description
        Added value: +"Desired output platforms, such as YouTube, Instagram, TikTok, Facebook, or LinkedIn. Planning does not publish."
  3. 1 tool update
    • Changedplan_clip_job5 fields changed
      • addedInput schema / properties / caption_mode
        Added value: +{
        +  "default": "burned_in",
        +  "enum": [
        +    "burned_in",
        +    "hook_only",
        +    "none"
        +  ],
        +  "type": "string"
        +}
      • addedInput schema / properties / complex_media
        Added value: +{
        +  "default": false,
        +  "type": "boolean"
        +}
      • addedInput schema / properties / creative_style
        Added value: +{
        +  "default": "clean",
        +  "enum": [
        +    "clean",
        +    "bold",
        +    "documentary",
        +    "property"
        +  ],
        +  "type": "string"
        +}
      • addedInput schema / properties / needs_deduplication
        Added value: +{
        +  "default": false,
        +  "type": "boolean"
        +}
      • addedInput schema / properties / needs_full_timeline
        Added value: +{
        +  "default": false,
        +  "type": "boolean"
        +}
  4. 2 tool updates
    • First observedget_clip_capabilities
    • First observedplan_clip_job

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.