Skip to main content
Glama

Frapea

get_bug_report

Prepare a BUG REPORT for the user: it opens in Frapea (Problems → Create bug report) for them to read and save. The report itself is NOT returned to you — it would leave the user's machine before they have seen it. You get a summary: open problems, media counts, and how many of the user's own words remain in composition code. It contains versions, problems with engine details, the project's structure with names and texts replaced, provider files by public id, the user's own files only as encoding fingerprints, and motion code. timelineIds limits it to those timelines and what they nest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesThe session token `connect` returned. Pass it on every call — it says which browser to drive.
projectIdYesProject id from get_projects (must be open in the editor).
timelineIdsNoOnly these timelines and the timelines they nest (default: all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources