OneSimpleAPI

POST /api/screenshot

api_post_screenshot

Destructive

Capture a screenshot of any webpage or HTML content Uses the OneSimpleAPI API (https://onesimpleapi.com/docs), with the same permissions, credits and storage. Supply API parameters in query or body. This tool always uses POST; do not supply method. Outputs preserve HTTP status, headers and JSON/text/base64 body; redirects are returned without following them.

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": "api_post_screenshot"
  }
}

Input Schema

Name	Required	Description
`body`	No	API request body. Nested objects, arrays, HTML, base64 data and all API options retain their original meaning.
`path`	No
`files`	No	Multipart uploads keyed by API field name (for example pdf). Supply file_name, base64 bytes and optional mime_type. Uploads use the existing API file validators.
`query`	No	URL query parameters. Sensitive API options must be in body as documented by the API.
`headers`	No	API request headers such as Idempotency-Key, Range and If-None-Match. Authentication and transport headers are managed by the connection.
`content_type`	No	Defaults to application/json, or multipart/form-data when files are supplied.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations declare destructive and open-world behavior, and the description adds real context beyond them: same permissions, credits and storage as the host API, HTTP status/headers preserved, and redirects returned unfollowed. It stops short of stating credit cost per call or what storage side effects mean for the caller.

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?

Three front-loaded sentences with no filler: capability, API provider, transport rule, then output behavior. The documentation URL earns its place; a slightly tighter framing could fold the POST rule into the first sentence.

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?

No output schema exists, and the description compensates by describing how results are returned (status, headers, JSON/text/base64 body, redirects unfollowed). For a tool with six top-level params and a large nested options object, the main gap is that it does not say a URL or HTML is required.

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 coverage is 83%, so the schema carries most parameter meaning; the description only adds placement guidance (query vs body). Many nested options are documented generically as "Existing API option; validated by the shared API implementation," and the description does nothing to clarify them.

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?

"Capture a screenshot of any webpage or HTML content" gives a specific verb and resource, and the OneSimpleAPI reference grounds it. It does not distinguish itself from near-neighbors like api_post_files_capture_link or api_post_pdf, so an agent must infer which capture endpoint applies.

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

Usage Guidelines3/5

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

The description provides transport-level usage rules: supply API parameters in query or body, always POST, never supply method. It gives no when-to-use guidance versus sibling tools (PDF, page info, capture link) and no prerequisites such as whether a URL or HTML is required.

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

All OneSimpleAPI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?