Skip to main content
Glama

tm_import_capture

Destructive

Import selected groups from an analysed JSONL capture as traffic profiles for load testing. Select groups by method and URL skeleton, and optionally name the profiles.

Instructions

Import the chosen groups from an analysed JSONL capture as real traffic profiles.

Workflow: call :func:tm_analyse_capture first to inspect the derived groups (method + URL skeleton + variables + RPS curve); pick the ones you want to persist; pass them here as selections.

capture_path must be the SAME JSONL file you analysed — server re-derives the analysis on commit (the preview response deliberately doesn't carry full per-row values, so trusting client-supplied preview data would be both heavy and tamper- able). The path resolves under $TM_MCP_CAPTURE_ROOT with the same security checks as tm_analyse_capture.

selections is a dict of shape::

{
    "groups": [
        {
            "method": "POST",
            "urlSkeleton": "https://api.example.com/api/x",
            "profileName": "load-test users"  # optional
        },
        ...
    ]
}

Each (method, urlSkeleton) pair must match a group returned by the prior tm_analyse_capture call exactly — index-based references would be fragile across re-analysis (groups sort by row count, ties break alphabetically). profileName is optional; omit / null lets the server pick a default like "[capture] POST /api/x". Empty groups list is allowed (no-op; result reports zero profiles created).

Returns the server's import result: createdProfiles (array of {profileId, name}), createdVariablesSetCount, skippedSelections (with reasons), warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
capture_pathYes
selectionsYes
Behavior4/5

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

Annotations include destructiveHint, idempotentHint, openWorldHint. Description adds that the server re-derives analysis on commit, and that empty groups is a no-op. No contradiction with annotations.

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?

Well-structured with workflow and parameter details in a clear order. Uses a block diagram for selections. Slightly verbose but each part adds value.

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

Completeness5/5

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

Given the complex import workflow and no output schema, the description covers the entire process, parameter details, and return value shape (createdProfiles, etc.). Complete guidance.

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

Parameters5/5

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

Schema coverage is 0%, but description thoroughly explains both parameters: capture_path must be same JSONL file with security checks; selections shape is given with detailed fields and constraints (exact match, optional profileName, empty allowed).

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 it imports groups from an analysed JSONL capture as real traffic profiles, distinguishing itself from tm_analyse_capture which only analyses and returns groups.

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?

It explicitly prescribes a workflow: call tm_analyse_capture first, then pass selections. It also explains constraints like using the same JSONL file and path resolution. Lacks explicit 'when not to use' but the workflow is clear.

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/trafficmorph-gif/tm-mcp'

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