Skip to main content
Glama

sonar

by app.trysonar

Export Screenshots (PNG)

sonar_export_screenshots
Read-only

Render a screenshot set to store-ready PNGs SERVER-SIDE (no browser needed) and save them as one ZIP per locale in output_dir — ready for App Store Connect / Play Console upload. Rendering happens through the same engine as the Screenshot Studio editor. Writes to the filesystem of the machine running the MCP server, so this tool is for local (stdio) use; over the hosted transport call GET /api/v1/screenshots/sets/:id/export directly instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
set_idYesScreenshot set id.
localesNoLocales to export (e.g. ["de-DE","ja"]). Use the set's source locale code for the source renders. Omit together with all_locales for source-only.
output_dirYesDirectory to write the ZIPs into (created if missing). One ZIP per locale, named <locale>.zip, each containing store-ready 01.png…NN.png.
all_localesNoExport the source locale plus every enabled locale.

TDQS

A3.9/5.0
Behavior1/5

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

The description truthfully discloses that the tool writes ZIP files to the filesystem, but the annotation declares readOnlyHint=true, which directly contradicts this write behavior. Since the description contradicts the annotation, a score of 1 is mandated per rubric rules.

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?

Three sentences with front-loaded action ('Render... save...'), no fluff. Every sentence earns its place: main operation, engine identity, and transport guidance. Efficient and scannable.

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?

Covers core functionality, usage location, and rendering engine well. However, the description omits return values (no output schema exists) and error handling. Combined with the annotation contradiction, the agent may be misled about safety. Adequate but has clear gaps.

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%, baseline 3. The description adds valuable meaning: it explains how locales and all_locales interact ('Omit together with all_locales for source-only'), names the ZIP file pattern (<locale>.zip), and clarifies output_dir behavior ('created if missing'). This goes beyond the schema's bare descriptions.

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 specifies the verb ('Render... and save'), resource ('screenshot set to store-ready PNGs'), and output ('one ZIP per locale'). It distinguishes itself from siblings like sonar_get_screenshot_set by focusing on export to filesystem, and explicitly mentions target stores (App Store Connect / Play Console).

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

Usage Guidelines5/5

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

Explicitly states when to use this tool ('local stdio use') and when not to ('over the hosted transport call GET /api/v1/screenshots/sets/:id/export directly instead'). This provides clear context and alternatives, leaving no ambiguity about transport restrictions.

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

All sonar toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool targets a distinct action or data aspect within the ASO domain. Keyword-related tools are clearly separated by purpose (tracked keywords vs. research vs. suggestions vs. metrics), and competitive tools differentiate between reading landscape and generating new analysis. No two tools have overlapping functionality that would confuse an agent.

Naming Consistency3/5

Naming is a mix of verb-first (e.g., sonar_add_screenshot, sonar_create_product) and noun-first patterns (e.g., sonar_app_keywords, sonar_competitor_landscape). While all use snake_case and the 'sonar_' prefix is consistent, the lack of a uniform verb_noun structure makes it harder to predict tool names. The pattern is readable but inconsistent.

Tool Count2/5

With 47 tools, the server is over-scoped for a typical MCP server. Although the ASO domain is broad, many tools are granular (e.g., 10 screenshot tools, 10 keyword tools). This quantity exceeds the 25+ threshold for 'too many' as defined in the calibration, making it heavy for an agent to navigate comprehensively.

Completeness5/5

The tool surface covers the full ASO lifecycle: app discovery, keyword research, tracking and ranking, competitor analysis, revenue estimation, screenshot creation and export, alerts, and product management. There are no obvious gaps—every necessary operation for monitoring and optimizing app store presence is present, including both read and write actions.

Resources