Skip to main content
Glama

instagram_reel_start

Starts a Reel download through Obscura and prepares local speech transcripts and sampled frames for analysis when supported.

Instructions

Start a Reel download through Obscura and local speech/frame preparation when supported.

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": {
      "url": "<url>"
    },
    "name": "instagram_reel_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
framesNo
refreshNo
languageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the description only needs to add job semantics. It does not disclose that this is an asynchronous start operation, whether it returns a job handle, whether repeated calls spawn duplicate downloads, or what "local speech/frame preparation" actually produces — all critical for a non-idempotent job launcher.

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

Conciseness3/5

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

A single sentence with no filler, which is good, but it is under-specified rather than efficient — the brevity comes at the cost of missing workflow and parameter information the agent needs.

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

Completeness2/5

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

For a four-parameter, non-idempotent job-starting tool with an output schema and zero schema descriptions, the definition should explain the URL input, the frames/language options, and how to retrieve results. None of that is present, leaving the definition inadequate for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description carries the full burden. It only loosely gestures at `frames` and `language` via "speech/frame preparation"; `refresh`, the frames range/default (1-24, 12), and what URL forms are accepted are entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Start a Reel download") plus an implementation detail (Obscura, local speech/frame preparation). However, "when supported" leaves the actual capability ambiguous, and nothing distinguishes it from siblings like instagram_reel_status or instagram_reel_artifact, which an agent would need to know about to use this correctly.

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 guidance on when to invoke this versus alternatives, no mention of prerequisites such as authenticating via instagram_login_start, and no indication that a follow-up call (status/artifact) is the expected next step. The agent is left to infer the entire workflow from the name.

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