Skip to main content
Glama

instagram_reel_artifact

Read transcript, manifest, contact sheet, or sampled frames from a completed Reel job by job ID and file name. Retrieve stored artifacts for local Reel analysis.

Instructions

Read transcript.txt, manifest.json, contact.jpg or frame_NNN.jpg from a completed job.

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": {
      "job_id": "<job_id>",
      "name": "<name>"
    },
    "name": "instagram_reel_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full load. It usefully discloses the whitelist of readable artifact names and the completion precondition, but says nothing about return format (text for transcript/manifest versus image bytes for contact.jpg and frames), failure modes for a missing artifact or an unfinished job, or whether frame_NNN is zero-padded or bounded. That leaves real behavioral gaps for a no-annotation tool.

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 sentence with zero filler, front-loading the verb and the artifact list. Nothing is redundant.

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?

There is no output schema and no annotations, and the artifact-specific return type is the single most important thing an agent needs to know here; it is absent. The definition also omits where job_id originates, leaving a two-parameter, output-varying tool partially specified.

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 0% and both properties are bare 'Name'/'Job Id' titles, so the description must compensate. It does define the valid domain of `name` concretely, which is valuable, but it does not explain `job_id` — where it comes from (start or status tool) or its format.

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?

States a specific verb (Read) with an enumerated set of resources (transcript.txt, manifest.json, contact.jpg, frame_NNN.jpg) and a scope qualifier ('from a completed job'). An agent can tell this retrieves job output files rather than job state, which separates it from instagram_reel_status, though no sibling is named explicitly.

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?

'from a completed job' implies the prerequisite that the job must have finished, which is useful gating context. However, it never says what to do instead while a job is running (presumably instagram_reel_status) or what happens if the requested artifact does not exist. Usage is implied rather than prescribed.

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