frida-ios-mcp

Overview Schema Source Related Servers Discussions Admin

media_upload

Upload local image or video files to the iOS device's DCIM/100APPLE folder for camera roll import.

Instructions

[advanced] AFC upload PC file to /DCIM/100APPLE/{IMG|VID}_XXXX.ext. Needs Python + pymobiledevice3. stage=upload on failure.

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": {
      "localPath": "<localPath>",
      "mediaType": "<mediaType>"
    },
    "name": "media_upload"
  }
}

Input Schema

Name	Required	Description
`udid`	No
`localPath`	Yes	Absolute path on this PC
`mediaType`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 27, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It mentions AFC upload but does not explain overwrite behavior, permission requirements, or the meaning of 'stage=upload on failure'.

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

Conciseness3/5

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

The description is brief and mostly to the point, but the cryptic note 'stage=upload on failure' is unclear and could be rephrased or expanded.

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

Completeness2/5

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

The description lacks information about return values, error handling, and the overall workflow. Given the tool's complexity (AFC upload to iPhone), it is incomplete without output schema or further context.

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?

With only 33% schema description coverage, the description does not add meaning to the parameters. It does not explain mediaType or udid beyond the schema, despite the low coverage.

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?

The description clearly states it uploads a PC file to a specific iPhone directory via AFC, distinguishing it from higher-level import tools like photos_import. However, the '[advanced]' tag is vague.

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?

The description mentions prerequisites (Python + pymobiledevice3) and a cryptic failure note, but does not specify when to use this tool over alternatives or provide exclusion criteria.

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