Skip to main content
Glama

Check a web app manifest's screenshots

check_pwa_screenshots
Read-onlyIdempotent

Check a web app manifest's screenshots against Chrome's rules for the richer install dialog without a browser: see which ones desktop and phone would display, and what to fix.

Instructions

Use it when the user wants to know whether a web app's install dialog will show screenshots, or a manifest's screenshots checked. Checks the screenshots a web app manifest lists against Chrome's rules for its richer install dialog, without a browser: which ones a desktop and a phone would show, and what to fix. A failed check is a normal result, with the report as its summary. It takes a pwa/manifest-screenshots.json from take_screenshots as it is; when the check fails for want of screenshots, take_screenshots with pwa makes ones that pass. The screenshots playbook (makersmcp_playbook) has the whole job. (easyscreenshotkit 0.1.3, on this machine.)

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": {
      "manifest": "<manifest>"
    },
    "name": "check_pwa_screenshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestYesThe manifest's file or address, or the site's address, like https://linear.app, when its page links the manifest. A pwa/manifest-screenshots.json from take_screenshots is checked as it is.
wait_secondsNoHow long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them.

Output Schema

NameRequiredDescriptionDefault
kitYes
docsNoThe notes the text shows, and where each one is.
nextNoWhat to do next, as the Next line says.
toolYes
filesNo
folderNoWhere the kit saved its files.
job_idYes
passedNoFor checks: whether the check passed.
statusYes
continuedNoTrue when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.
exit_codeNo
last_lineNoWhat the kit was doing last.
expires_atNoWhen the download links stop working.
next_actionNo
elapsed_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / manifest / description
      Previous value: -"The manifest's file or address, or the site's address, like https://linear.app."New value: +"The manifest's file or address, or the site's address, like https://linear.app, when its page links the manifest. A pwa/manifest-screenshots.json from take_screenshots is checked as it is."
    • changedInput schema / properties / wait_seconds / description
      Previous value: -"How long to wait for the result before returning a job_id to wait on. 45 is safe for clients that stop a tool call after 60 seconds."New value: +"How long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them."
    • addedOutput schema / properties / continued
      Added value: +{
      +  "description": "True when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / docs
      Added value: +{
      +  "description": "The notes the text shows, and where each one is.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "path": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / next
      Added value: +{
      +  "description": "What to do next, as the Next line says.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered; the description adds genuinely new behavior: it runs without a browser, reports per-device (desktop vs phone) results plus fixes, and clarifies that a failed check is a normal result returned as the report rather than an error. It also states that a take_screenshots manifest-screenshots.json is accepted as-is.

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?

Ordering is sensible: when to use, what it does, failure semantics, alternatives, then provenance. Most sentences carry weight, but the opening clause 'or a manifest's screenshots checked' is grammatically awkward and the trailing '(easyscreenshotkit 0.1.3, on this machine.)' is low-value packaging detail.

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

Completeness4/5

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

With an output schema present and 100% param coverage, the description only needs to frame the job, which it does well, including the no-browser and normal-failure semantics. The async job_id behavior is left entirely to the wait_seconds schema description, a minor gap for a tool that may return a job handle.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented in detail, including the accepted manifest forms and the wait_seconds/job_id fallback. The description echoes the 'take_screenshots output works as-is' point but adds no syntax, format, or default guidance beyond the schema, so baseline 3 applies.

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?

States a concrete verb and resource: checks the screenshots a manifest lists against Chrome's rules for the richer install dialog, without a browser. It also names what the output covers (which ones desktop and phone would show, and what to fix), so an agent can tell it apart from take_screenshots, which produces rather than validates the files.

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?

Opens with the exact user intent that selects this tool (does the install dialog show screenshots / check a manifest's screenshots) and then names the alternative path: when the check fails for want of screenshots, call take_screenshots with pwa. It also points to makersmcp_playbook for the full job, so both the when and the follow-up are explicit.

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