Skip to main content
Glama

profiler-load

Restore a saved profiling session from disk to memory. List available sessions, then load React or native profiler data for query tools to analyze.

Instructions

Fetch and restore a previously captured profiling session from disk into memory so query tools can operate on it. This is the disk-restore counterpart to react-profiler-stop/native-profiler-stop, which write data, and to the query tools (profiler-cpu-query, profiler-commit-query, profiler-stack-query), which read it. Use when you need to revisit past session data without capturing a new recording. Modes:

  • list: Show all available profiling sessions in the project's debug directory.

  • load_react: Load a React profiler session (CPU profile + commit tree) into memory. Requires session_id.

  • load_native: Re-parse native profiler XML files into memory. Requires session_id and device_id. For Android .pftrace restores, pass app_process for older sessions that do not have a metadata sidecar. Returns a summary of the loaded session or a session list for the list mode. Fails if the session_id is not found or required XML files are missing from disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYeslist: show available sessions on disk. load_react: load a React profiler session into memory for query tools. load_native: re-parse native profiler XML files (xctrace on iOS) into memory for query tools.
portNoMetro port — the loaded React data is cached under this port for query tools (default 8081)
device_idYesTarget device id from `list-devices`. Used to cache the loaded React session under the correct port+device key, and required to resolve the native profiler session for load_native.
session_idNoTimestamp-based session identifier (e.g. '20250313-143022') from the list output. Required for load_react and load_native modes.
app_processNoAndroid package name to use when restoring older load_native .pftrace sessions that do not have a metadata sidecar.
Behavior4/5

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

With no annotations provided, the description details disk-to-memory loading, caching behavior, failure conditions (missing session_id/XML files), and special handling for Android .pftrace. It does not mention side effects like overwriting existing loaded data.

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

Conciseness4/5

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

The description is well-structured with mode breakdown. It is slightly verbose but information-dense. Every sentence adds value.

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

Completeness4/5

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

Given 5 parameters, no output schema, and many sibling profiling tools, the description covers the lifecycle and prerequisites well. It lacks details on the return format of the summary.

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

Parameters4/5

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

Schema coverage is 100%. The description adds context beyond schema: required modes for session_id, caching under port+device key, and app_process for older sessions.

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

Purpose5/5

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

The description clearly states the verb (fetch/restore), resource (profiling session), and outcome (into memory for query tools). It distinguishes itself from sibling tools like capture (react-profiler-stop) and query tools (profiler-cpu-query).

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

Usage Guidelines4/5

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

The description explicitly says when to use ('revisit past session data without capturing a new recording') and describes the three modes. It references sibling tools as counterparts but does not explicitly state when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/software-mansion/argent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server