Skip to main content
Glama
Sign In
Mobile Design MCP

Mobile Design MCP

by noxpublishing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_recordings

Read-onlyIdempotent

List imported local media for mobile design review, with optional inline screenshot previews to verify app flows. Filter by app, platform, and result limit.

Instructions

List imported local media, optionally with up to two inline screenshot previews.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_recordings"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdNo
limitNo
platformNo
previewsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds one genuinely new behavioral detail — that previews are inlined and capped at two screenshots — but says nothing about pagination, ordering, or whether results are scoped to local imports only.

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?

One front-loaded sentence with no filler; the core action comes first and the optional qualifier trails it. It is appropriately sized, though the brevity is partly the source of the semantic gaps.

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?

Four optional parameters with zero schema descriptions and no output schema means the description has the entire burden of explaining call semantics, and it explains only one of the four. An agent still cannot tell what a recording is, what appId filters, or what a default page of 12 returns.

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%, so the description must carry parameter meaning, and it does not. It never explains appId, limit, or platform; even the previews mention ('up to two inline screenshot previews') is ambiguous against a boolean flag, leaving the reader unsure whether 'two' refers to a count or a cap per request.

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?

States a specific verb and resource: 'List imported local media.' An agent can tell this is a listing tool for recordings, though the description switches vocabulary from 'recordings' to 'media' and never contrasts itself with siblings like list_motion_recipes or mobbin_search_screens.

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 phrase 'optionally with up to two inline screenshot previews' hints at a light vs. heavy listing mode, but there is no explicit when-to-use, when-not-to-use, or named alternative among the 16 siblings. The agent must infer the tool's role.

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