Skip to main content
Glama

upload_page_snapshot

Upload a full-page screenshot to create an annotated page with numbered pin markers at true positions, enabling viewers to click and open thread bubbles for visual feedback on a live app.

Instructions

Upload a full-page screenshot that turns the public share report into an annotated page: viewers see the real page with numbered pin markers at true positions and click-to-open thread bubbles. Capture the page yourself (kill animations, scroll to force lazy loads, full-page shot, JPEG/WebP ≤5MB), resolve each open pin's element.selector to document-pixel coordinates IN THAT CAPTURE, and pass them as pinPositions. Owner/editor only. One snapshot per (project, page) — re-upload replaces it. pageUrl must match the pins' page_url verbatim.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthYesPixel width of the uploaded image (1–4000). Pin coordinates must be in this same space.
heightYesPixel height of the uploaded image (1–60000).
pageUrlYesExact page_url the pins carry — copy verbatim from get_annotations. The snapshot is keyed by this string.
imageB64NoBase64 image data, if imagePath is not available.
imagePathNoAbsolute path to the JPEG/WebP file on disk (preferred — read server-side, keeps base64 out of the transcript).
projectIdYesThe project ID
contentTypeNoDefault image/jpeg. PNG is rejected for page snapshots (size).
pinPositionsNoDocument-pixel coordinates of each pin in THIS image, resolved from element.selector at capture time. Pins omitted here render in the notes list only.
Behavior4/5

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

Without annotations, description covers auth requirements (owner/editor only), destructive behavior (re-upload replaces), image constraints (≤5MB, JPEG/WebP), and pageUrl matching requirement. Missing rate limits but sufficient.

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?

Single paragraph efficiently covers all key points without fluff. Front-loaded with purpose. Could be slightly more structured but remains concise.

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?

Given 8 parameters (4 required) and no output schema, description provides comprehensive workflow, parameter usage, and constraints. Lacks return value details but tool is action-oriented.

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% but description adds significant context: explains imageB64 vs imagePath preference, pinPositions coordinate meaning, contentType defaults to JPEG, and that omitted pins render in notes list. Adds value beyond schema.

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?

Description clearly states verb 'Upload a full-page screenshot' and specific resource 'turn public share report into an annotated page'. It distinguishes from siblings by being the only tool handling snapshot upload with pin mapping.

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

Usage Guidelines4/5

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

Provides explicit preparation steps (kill animations, scroll, etc.) and permissions ('Owner/editor only'). Does not contrast with alternatives but context implies uniqueness.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jcooley8/pincushion-plugin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server