Skip to main content
Glama

Social Fetch

by io.github.social-freak-ltd

Capture website screenshot

web_screenshot_capture
Read-only

Capture a screenshot of a public web page URL as a hosted image artifact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesWeb page URL to fetch.
delayNoExtra settle delay in milliseconds after load (0–10000).
formatNoOutput image format. Default: png.png
regionNoOptional ISO 3166-1 alpha-2 country for geo-located rendering (+1 credit).
qualityNoJPEG/WebP quality 1–100. Invalid when format is png.
waitForNoCSS selector to wait for before capturing.
blockAdsNoBlock ads and trackers during render. Default: true.
cacheTtlNoOptional Redis artifact-cache TTL in seconds (60–604800). Must stay strictly below the 7-day object lifetime.
darkModeNoRequest prefers-color-scheme: dark. Default: false.
fullPageNoWhen true, capture the full scrollable page. Default: false (viewport).
responseNoDelivery mode. `url` (default) returns a hosted CDN URL valid for 7 days. `base64` returns the image bytes inline when small enough.url
selectorNoCSS selector to clip the screenshot to a single element. Cannot be combined with fullPage.
cacheModeNoCache behavior. `enabled`: read from cache if present, else fetch and write to cache. `bypass`: always fetch fresh, ignoring and not updating the cache. `write_only`: always fetch fresh, but write the result to cache without reading from it first. Default: `enabled`.enabled
waitUntilNoNavigation wait condition. `networkidle` is bounded and resolves on idle or a short cap, whichever comes first. Default: load.load
viewportWidthNoViewport width in CSS pixels. Default: 1280.
viewportHeightNoViewport height in CSS pixels. Default: 800.
deviceScaleFactorNoDevice scale factor (1–3). Default: 1.
blockCookieBannersNoDismiss/block cookie consent banners. Default: true.

TDQS

A3.6/5.0
Behavior3/5

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

The annotations (readOnlyHint: true, openWorldHint: true) already cover the read-only and external network access behavior. The description adds the 'hosted image artifact' detail, which hints at the return format, but it does not disclose other behavioral aspects like the 7-day artifact lifetime, caching behavior, or that it might fetch external resources. Given the annotations, a score of 3 is appropriate—the description provides a small extra but not significant behavioral context.

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?

The description is a single, well-structured sentence with the action front-loaded. It is extremely concise with zero fluff, conveying the core purpose in eight words. This is an ideal length for a tool description.

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 the tool has 18 parameters, the schema fully documents them, and the description explicitly states the output type ('hosted image artifact'), the definition is largely complete. It lacks explicit mention of the 7-day URL validity and that the output is a URL by default, but these are captured in the 'response' parameter description. The presence of the output type in the description compensates for the lack of an output schema, and the schema handles the rest.

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?

The input schema has 100% coverage with detailed descriptions for all 18 parameters, including enums, defaults, and constraints. The tool description adds no parameter-specific information beyond what the schema already provides. Since the schema does the heavy lifting, the baseline of 3 holds—no additional value is contributed by the description.

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 states the action (Capture), the resource (screenshot of a public web page URL), and the output (hosted image artifact). It is concise and unambiguous, differentiating this tool from other web tools (e.g., web_extract_run, web_html_generate) by focusing specifically on screenshots.

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 gives no guidance on when to use this tool versus alternatives (e.g., web_extract_run for text extraction, web_ask_run for questions). It does not mention limits like public URLs only, nor does it state when not to use it. There is no explicit routing or exclusion logic, leaving the agent to infer usage solely from the tool name and schema.

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

All Social Fetch 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

B3.4/5.0
Disambiguation5/5

Each tool is clearly scoped to a specific platform and action (e.g., facebook_post_get vs instagram_post_get). Descriptions explicitly differentiate similar tools across platforms, and within-a-platform tools like tiktok_search_videos_list vs tiktok_search_hashtag_list have clear disambiguation notes.

Naming Consistency5/5

All 167 tools follow a strict `platform_resource_action` pattern (e.g., youtube_video_comments_list). No mixing of styles—snake_case throughout, with consistent verb ordering (get, list, search, etc.).

Tool Count2/5

The server has 167 tools, which is far beyond the typical well-scoped range of 3-15. While the broad multi-platform scope justifies many tools, this extreme number makes the tool surface overwhelming and difficult for an agent to navigate efficiently.

Completeness4/5

The tool set covers a wide range of platforms and operations including profile retrieval, post/video fetching, comments, search, transcripts, and ad library access. Minor gaps exist (e.g., no Facebook events or LinkedIn messaging), but the surface is comprehensive for a read-only data aggregation use case.

Resources