Skip to main content
Glama
Sign In

OneSimpleAPI

by com.onesimpleapi
OverviewDiscussionsAdmin

POST /api/page_info

api_post_page_info
Destructive

Extract metadata from web pages including title, description, Open Graph, and Twitter cards 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_page_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoAPI request body. Nested objects, arrays, HTML, base64 data and all API options retain their original meaning.
pathNo
filesNoMultipart 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.
queryNoURL query parameters. Sensitive API options must be in body as documented by the API.
headersNoAPI request headers such as Idempotency-Key, Range and If-None-Match. Authentication and transport headers are managed by the connection.
content_typeNoDefaults to application/json, or multipart/form-data when files are supplied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, destructiveHint=true and readOnly=false; the description adds real context beyond them: shared API permissions/credits/storage, POST-only invocation, and that responses preserve HTTP status, headers and body while redirects are returned unfollowed. It does not explain why a metadata read is flagged destructive (credit consumption / external side effects), which would help an agent reason about the annotation.

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?

The payload-relevant information is front-loaded in the first sentence, with operational caveats after it. Some wording is run-on and under-punctuated ('Twitter cards Uses the OneSimpleAPI API'), but no sentence is filler.

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 six parameters, nested objects and no output schema, the description does the heavy lifting on response shape (status/headers/body preserved, redirects not followed), which is exactly what an output-schema-less tool needs. The remaining gap is choosing between this and sibling URL-analysis endpoints.

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 high (83%) and the nested body/query properties already document url, output and headers, including the output enum options. The description only adds placement guidance ('query or body'), and the schema itself carries the finer point that sensitive options must live in body.

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?

States a specific verb and resource ('Extract metadata from web pages') and enumerates the returned fields (title, description, Open Graph, Twitter cards), so the agent knows exactly what the call produces. It does not differentiate from closely related siblings like api_post_page_status or api_post_readability, which also operate on a URL and could plausibly return page data.

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 only guidance is mechanical ('supply API parameters in query or body', 'do not supply method'), not decision-oriented. There is no statement of when to choose this over api_post_page_status, api_post_readability, or api_post_screenshot, and no prerequisites or exclusions beyond the method restriction.

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

All OneSimpleAPI toolsInspect
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