Skip to main content
Glama

Unload Frida Script

unload_frida_script

Removes a selected Frida script from a live session, detaching its instrumentation from the target and stopping that script's hooks.

Instructions

Unload one caller-selected Frida script from a live session. This removes that script's instrumentation from the target.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "script_id": "00000000-0000-4000-8000-000000000002",
      "session_id": "00000000-0000-4000-8000-000000000001"
    },
    "name": "unload_frida_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
script_idYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is partly covered. The description usefully narrows the blast radius (only that one script's instrumentation is removed from the target) but says nothing about repeat calls (idempotentHint=false), failure when the script is not loaded, or what the caller gets back.

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?

Two short sentences, front-loaded with the action and resource, with the effect statement second and no filler. 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?

For a two-parameter mutation tool with no output schema and zero schema documentation, the definition covers the what and the scope but not the operational edges: active-session requirement, behavior on a stale or already-unloaded script_id, and any return indication of success. Adequate but with clear gaps.

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% — the two parameters are only typed as UUIDs with no documentation. The description hints at two concepts ("one ... Frida script" and "live session") but never ties them to script_id or session_id, gives no format/validity constraints, and does not explain whether they must reference a currently-attached script.

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?

"Unload one caller-selected Frida script from a live session" gives a specific verb (unload), resource (Frida script), and scope (single script, live session), and the second sentence clarifies the effect as removal of instrumentation. It is clearly the inverse of load_frida_script, though it never names that sibling explicitly.

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 when-to-use or when-not-to-use guidance, no prerequisites (e.g., the script must currently be loaded and its session still open), and no mention of alternatives such as close_frida_session for tearing down everything. Usage is only faintly implied by "from a live session."

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

Deploy Server

Other Tools